Skip to content

Conversation

@HadleyKing
Copy link
Collaborator

No description provided.

	modified:   bco_api/bco_api/settings.py
	modified:   bco_api/server.conf
Changes to be committed:
	modified:   bco_api/api/permissions.py
	modified:   bco_api/server.conf
Changes to be committed:
	modified:   bco_api/api/model/groups.py
	modified:   bco_api/api/model/prefix.py
	modified:   bco_api/api/scripts/method_specific/POST_api_objects_drafts_modify.py
	modified:   bco_api/api/views.py
	modified:   bco_api/bco_api/settings.py
Changes to be committed:
	modified:   Dockerfile
	modified:   admin_only/bco_api.conf
	modified:   bco_api/bco_api/settings.py
	modified:   bco_api/server.conf
	new file:   docker-compose.yml
Changes to be committed:
	new file:   .github/workflows/publish-Docker-image
Changes to be committed:
	renamed:    .github/workflows/publish-Docker-image -> .github/workflows/release-package.yml
Changes to be committed:
	modified:   Dockerfile
	deleted:    apitests.py
	deleted:    apitests_new.py
	deleted:    bco_api/static/img/android-chrome-192x192.png
	deleted:    bco_api/static/img/android-chrome-512x512.png
	deleted:    bco_api/static/img/apple-touch-icon.png
	deleted:    bco_api/static/img/favicon-16x16.png
	deleted:    bco_api/static/img/favicon-32x32.png
	deleted:    bco_api/static/img/favicon.ico
	deleted:    cag.sh
	deleted:    curl_fetch.txt
	modified:   docker-compose.yml
Changes to be committed:
	modified:   bco_api/api/model/groups.py
	modified:   bco_api/api/model/prefix.py
	modified:   bco_api/api/models.py
	modified:   bco_api/api/permissions.py
	modified:   bco_api/api/scripts/utilities/JsonUtils.py
	modified:   bco_api/bco_api/settings.py
	modified:   bco_api/server.conf
@gitguardian
Copy link

gitguardian bot commented Nov 16, 2022

⚠️ GitGuardian has uncovered 5 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id Secret Commit Filename
4444553 Company Email Password f96b769 Dockerfile View secret
4444553 Company Email Password f426dc4 Dockerfile View secret
4444554 Generic High Entropy Secret f426dc4 apitests.py View secret
4444554 Generic High Entropy Secret f426dc4 apitests.py View secret
4444553 Company Email Password f426dc4 docker-compose.yml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

@HadleyKing HadleyKing merged commit e22f99e into main Nov 16, 2022
@HadleyKing HadleyKing deleted the 22.11 branch November 16, 2022 15:40
# Append the possible "errors".
if any_failed and len(return_data) == 1:
return Response(status=return_data[0]['status_code'], data=return_data)
return Response(status=return_data[0]["status_code"], data=return_data)

Check warning

Code scanning / CodeQL

Reflected server-side cross-site scripting

Cross-site scripting vulnerability due to a [user-provided value](1). Cross-site scripting vulnerability due to a [user-provided value](2). Cross-site scripting vulnerability due to a [user-provided value](3). Cross-site scripting vulnerability due to a [user-provided value](4). Cross-site scripting vulnerability due to a [user-provided value](5). Cross-site scripting vulnerability due to a [user-provided value](6). Cross-site scripting vulnerability due to a [user-provided value](7). Cross-site scripting vulnerability due to a [user-provided value](8). Cross-site scripting vulnerability due to a [user-provided value](9). Cross-site scripting vulnerability due to a [user-provided value](10). Cross-site scripting vulnerability due to a [user-provided value](11). Cross-site scripting vulnerability due to a [user-provided value](12). Cross-site scripting vulnerability due to a [user-provided value](13). Cross-site scripting vulnerability due to a [user-provided value](14). Cross-site scripting vulnerability due to a [user-provided value](15). Cross-site scripting vulnerability due to a [user-provided value](16). Cross-site scripting vulnerability due to a [user-provided value](17). Cross-site scripting vulnerability due to a [user-provided value](18).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants