-
-
Notifications
You must be signed in to change notification settings - Fork 148
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
Update to SnakeYAML 1.26 to address CVE-2017-18640 #187
Comments
Updated for 2.10(.4); backported in 2.9 branch but uncertain whether there will be any releases (if so, 2.9.10.1 or 2.9.11) |
@cowtowncoder Thanks for your swift reaction! |
No prob, thank you for bringing this CVE to our attention. |
SnakeYAML < 1.26 is vulnerable to a Billion Laughs attack (denial of service). * https://nvd.nist.gov/vuln/detail/CVE-2017-18640 * https://bitbucket.org/asomov/snakeyaml/issues/377 Refs FasterXML/jackson-dataformats-text#187 Refs #3223
SnakeYAML < 1.26 is vulnerable to a Billion Laughs attack (denial of service). * https://nvd.nist.gov/vuln/detail/CVE-2017-18640 * https://bitbucket.org/asomov/snakeyaml/issues/377 Refs FasterXML/jackson-dataformats-text#187 Refs #3223
SnakeYAML < 1.26 is vulnerable to a Billion Laughs attack (denial of service). * https://nvd.nist.gov/vuln/detail/CVE-2017-18640 * https://bitbucket.org/asomov/snakeyaml/issues/377 Refs FasterXML/jackson-dataformats-text#187 Refs #3223
Even after this commit, I still see SnakeYAML 1.23 is getting pulled via DropWizard 1.3.22. From dropwizard-bom-1.3.22.pom, I see it is correctly pointing to SnakeYAML 1.26 but SnakeYAML 1.23 is getting pulled via DropWizard 1.3.22 |
@nandakishorkn I'm unable to reproduce this with a new project (generated using the Dropwizard Maven archetype). Maybe you or a dependency in your project overrides the version of SnakeYAML? Please create an issue at https://github.com/dropwizard/dropwizard/issues with a minimal project to reproduce your issue if you cannot find the reason. Here's the example:
|
SnakeYAML < 1.26 is vulnerable to a Billion Laughs attack (denial of service).
The issue has been tracked in asomov/snakeyaml#377 and been published in CVE-2017-18640.
References:
The text was updated successfully, but these errors were encountered: