Repository navigation
fix(a5): improve stegonography security configuration - #659
Open
gabrielesequeira wants to merge 1 commit into
Open
gabrielesequeira wants to merge 1 commit into
gabrielesequeira wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This solution refers to which of the apps?
A5 - Security Misconfiguration (Stegonography)
What did you do to mitigate the vulnerability?
ADMIN_PASSWORD), generated through the environment configuration script.throw errstatements with controlled error handling to prevent exposing internal exceptions and stack details to users, returning generic error responses instead.- Disabled theX-Powered-ByHTTP header to prevent exposing the Express technology information.HttpOnly,SameSite=Strict, andSecurein production.SECRETmongod --auth.authSource=admin.node:22-bookworm-slimto suport the updates.package-lock.json.Did you test your changes? What commands did you run?
Yes. Changes were tested locally and manually.
Commands executed:
make install docker exec Stegonography_api node -v docker logs Stegonography_api --tail 100Test results: