[GHSA-3mcp-9wr4-cjqf] Remote Code Execution (RCE) vulnerability in dropwizard-validation

[poc-effectiveness]

Updates

• Affected products

Comments
We are writing to report an inconsistency between the affected version range listed for CVE-2020-5245 in the GitHub Advisory Database and the version range provided by the NVD:

🔗 https://nvd.nist.gov/vuln/detail/CVE-2020-5245

According to NVD, the affected versions are defined as:

Dropwizard-Validation before 1.3.19 and before 2.0.2

This implies that the following versions are vulnerable:

1.3.0-rc1 through 1.3.0-rc7

2.0.0-rc0+test8 through 2.0.0-rc14

We have verified this through testing, and have confirmed that these versions are indeed vulnerable. To support this, we have published PoCs for reproduction and validation:

For 1.3.0-rc1 through 1.3.0-rc7:
🔗 https://github.com/poc-effectiveness/PoCAdaptation/tree/main/Adapted/CVE-2020-5245

For 2.0.0-rc0+test8 through 2.0.0-rc14:
🔗 https://github.com/poc-effectiveness/PoCAdaptation/tree/main/Origin/CVE-2020-5245/exploit

We respectfully request that the advisory be updated to reflect the accurate affected version range.

[github]

Hi there @joschi! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.

This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory

[joschi]

@poc-effectiveness Are you a bot? Was this change generated using "AI" (some sort of LLM)?

[poc-effectiveness]

Dear @joschi ,

I am not a bot, the change is generated manually according to our research focus on PoC migration, which means adapting a valid PoC for a library vulnerability to target versions and analyze the impact of the vulnerability on target versions. Our modified PoC and affected versions are examined by three authors of our research (each with five year experience in library vulnerabilities).

For convenience, our discussion template is generated by AI, but we manually fill contents, such as affected version and reference link.

[advisory-database]

Hi @poc-effectiveness! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future!