Configure Mend for GitHub.com #8
Open
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
![mend-for-github-com[bot]](https://avatars.githubusercontent.com/in/30796?s=60&v=4){kind=small}
…dant (NeuraLegion#319) Co-authored-by: Anatol Karalkoŭ <[email protected]> Return default chart names
…rable to date manipulation (NeuraLegion#320)
Update README.md
A client side endpoint that is vulnerable to prototype pollution --------- Co-authored-by: Tamir Gershberg <[email protected]>
- rework redundant `npm ci` calls - CYPRESS_INSTALL_BINARY=0 to skip downloading chromium relates-to NeuraLegion#319
Co-authored-by: Anatol Karalkoŭ <[email protected]> Co-authored-by: denanmusinovic <[email protected]> Co-authored-by: Denan Musinovic <[email protected]> Co-authored-by: Viachaslau <[email protected]> Co-authored-by: Bar Hofesh <[email protected]>
…to-regexp` vuln) (NeuraLegion#409)
Useful for situations when the exact version of docker image needs to be provided
…ore` 10.4.2 to 10.4.7 (NeuraLegion#420)
This PR addresses two issues in the SQL KID processor which prevent it being exploitable in the intended fashion. 1. The code following the SQL query assumes a single result returned by the query, while the `execute` method uses the default "all" method which returns a list of results. This has been modified to use the "get" method which will return a single result. 2. After the query has been executed, the key used is still always the default key, rather than the one returned by a query. This means that the JWT will only be validated if signed using the default key rather than an attacker-specified key. This has been modified to always use the key returned by the query, allowing the attacker to control the key used to sign the token.
|
New Issues (107)Checkmarx found the following issues in this Pull Request
Fixed Issues (2004)Great job! The following issues were fixed in this Pull Request
|
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.
Welcome to Mend for GitHub.com (formerly WhiteSource). This is an onboarding PR to help you understand and configure settings before Mend starts scanning your repository for security vulnerabilities.
🚦 Mend for GitHub.com will start scanning your repository only once you merge this Pull Request. To disable Mend for GitHub.com, simply close this Pull Request.
What to Expect
This PR contains a '.whitesource' configuration file which can be customized to your needs. If no changes were applied to this file, Mend for GitHub.com will use the default configuration.
Before merging this PR, Make sure the Issues tab is enabled. Once you merge this PR, Mend for GitHub.com will scan your repository and create a GitHub Issue for every vulnerability detected in your repository.
If you do not want a GitHub Issue to be created for each detected vulnerability, you can edit the '.whitesource' file and set the 'minSeverityLevel' parameter to 'NONE'.
If Mend Remediate Workflow Rules are set on your repository (from the Mend 'Integrate' tab), Mend will also generate a fix Pull Request for relevant vulnerabilities.
❓ Got questions? Check out Mend for GitHub.com docs.
If you need any further assistance then you can also request help here.