-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Block some more DBCP-related potential gadget classes (CVE-2020-36179 - CVE-2020-36182) #3004
Comments
cowtowncoder
added
CVE
Issues related to public CVEs (security vuln reports)
to-evaluate
Issue that has been received but not yet evaluated
and removed
to-evaluate
Issue that has been received but not yet evaluated
labels
Jan 1, 2021
The following CVEs have been assigned to this issue: |
cowtowncoder
changed the title
Block one more DBCP-related potential gadget class
Block some more DBCP-related potential gadget classes
Jan 7, 2021
cowtowncoder
changed the title
Block some more DBCP-related potential gadget classes
Block some more DBCP-related potential gadget classes
Jan 7, 2021
cowtowncoder
changed the title
Block some more DBCP-related potential gadget classes
Block some more DBCP-related potential gadget classes (CVE-2020-36179 - CVE-2020-36182)
Jan 7, 2021
This was referenced Jan 9, 2021
This was referenced Dec 25, 2022
This was referenced Dec 20, 2022
Open
Open
This was referenced Feb 17, 2023
Open
Open
Open
This was referenced Nov 22, 2022
This was referenced Mar 15, 2023
This was referenced Feb 15, 2023
This was referenced May 25, 2023
This was referenced May 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One additional, not-yet-blocked type of Apache DBCP (1.x/2.x) library was reported as possible gadget type and should be blocked.
See https://medium.com/@cowtowncoder/on-jackson-cves-dont-panic-here-is-what-you-need-to-know-54cd0d6e8062 for description of the general problem.
Reporter(s): Al1ex@knownsec
Mitre id(s):
Fix is included in:
The text was updated successfully, but these errors were encountered: