Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug fixes --> Security Fix #55

Merged
merged 3 commits into from
Feb 5, 2024
Merged

Bug fixes --> Security Fix #55

merged 3 commits into from
Feb 5, 2024

Conversation

tylerlight071
Copy link
Owner

Fixed all security vulnerabilities by changing libraries and ensuring more computing power is used when creating hash

- Fixed vulnerability by switching libraries and ensuring that the hashed password uses more computing power and is more secure as a cryptographic system
- Updated V0.4 to also include this fix too
@tylerlight071 tylerlight071 added the Security Security Vulnerabilities label Feb 5, 2024
@tylerlight071 tylerlight071 self-assigned this Feb 5, 2024
Copy link

gitguardian bot commented Feb 5, 2024

⚠️ GitGuardian has uncovered 2 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 GitGuardian status Secret Commit Filename
9468690 Triggered MongoDB Credentials c004725 config.py View secret
9468690 Triggered MongoDB Credentials 5636f32 config.py 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!

@tylerlight071
Copy link
Owner Author

All secret leaks are fixed and the key has been destroyed. Small issue due to config.py holding my database URI rather than the default upon push

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment