rules:feat - adding rule to spring framework rce #1053
Merged
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
nathanmartinszup
force-pushed
the
feature/spring-framework-vuln
branch
from
cb09f54 to
bff71b0
Compare
This commit adds a new rule to identify a new remote code execution vulnerability in the spring framework. Due to the limitations of the regex engine, this rule can bring some false positives about safe versions pointed out as vulnerabilities. The rule will consider any vulnerability < 5.3.18 as vulnerable, which is not true, as versions >= 5.2.20 already have the fix for the problem, but due to the limitation of the engine we can't detect it. Signed-off-by: Nathan Martins <nathan.martins@zup.com.br>
nathanmartinszup
force-pushed
the
feature/spring-framework-vuln
branch
from
bff71b0 to
6f760ec
Compare
wiliansilvazup
approved these changes
Apr 4, 2022
nathanmartinszup
requested review from
matheusalcantarazup,
lucasbrunozup and
oliveirafelipezup
as code owners
wiliansilvazup
approved these changes
Apr 4, 2022
|
I'll merge this PR first to release new patch |
nathanmartinszup
added a commit
that referenced
this pull request
Apr 4, 2022
This commit adds a new rule to identify a new remote code execution vulnerability in the spring framework. Due to the limitations of the regex engine, this rule can bring some false positives about safe versions pointed out as vulnerabilities. The rule will consider any vulnerability < 5.3.18 as vulnerable, which is not true, as versions >= 5.2.20 already have the fix for the problem, but due to the limitation of the engine we can't detect it. Signed-off-by: Nathan Martins <nathan.martins@zup.com.br> (cherry picked from commit e5a7fd0)
nathanmartinszup
added a commit
that referenced
this pull request
Apr 4, 2022
This commit adds a new rule to identify a new remote code execution vulnerability in the spring framework. Due to the limitations of the regex engine, this rule can bring some false positives about safe versions pointed out as vulnerabilities. The rule will consider any vulnerability < 5.3.18 as vulnerable, which is not true, as versions >= 5.2.20 already have the fix for the problem, but due to the limitation of the engine we can't detect it. Signed-off-by: Nathan Martins <nathan.martins@zup.com.br> (cherry picked from commit e5a7fd0)
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 commit adds a new rule to identify a new remote code execution
vulnerability in the spring framework. Due to the limitations of the
regex engine, this rule can bring some false positives about safe
versions pointed out as vulnerabilities. The rule will consider
any vulnerability < 5.3.18 as vulnerable, which is not true, as
versions >= 5.2.20 already have the fix for the problem, but due
to the limitation of the engine we can't detect it.
Signed-off-by: Nathan Martins nathan.martins@zup.com.br
- What I did
- How to verify it
- Description for the changelog