commonlib: add more details to "Information Leakage" vulnerability #5834
Conversation
This file contains 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
Adds more solutions and reference links to Information Leakage vulnerability. Signed-off-by: joshua530 <[email protected]>
|
All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
|
CHANGELOG.md should also be updated. I'm sure if you scroll a bit you can find related previous entries. |
Adds more solutions and reference links to Information Leakage vulnerability. Signed-off-by: joshua530 <[email protected]>
|
My apologies for forgetting. I've made the changes. |
|
Note for the team - the vulnerabilities.xml file was originally imported from the WASC website. |
kingthorin
reviewed
Oct 29, 2024
| * Store sensitive data only if you have to. | ||
| * Implement checks for sensitive information in your devops pipeline. Steps that could be taken include stripping developer comments, removing debugging information and sensitive logs, as well as making error messages less verbose. | ||
| * In situations where the sensitive information must be used, for instance, backend microservices, ensure trust boundaries are appropriately drawn. Example: set up an isolated, well secured kubernetes cluster with well configured access controls, then only grant access to authorized clients. | ||
| * In situations where error messages need to be returned to the user, use messages that are as generic as possible eg "invalid credentials" instead of "invalid username" or "invalid password" |
There was a problem hiding this comment.
Add a period for consistency
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.
Adds more solutions and reference links to Information Leakage vulnerability.
Part of zaproxy/zaproxy#8056