We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Uncontrolled recursion leads to abort in deserialization
yaml-rust
0.3.5
>=0.4.1
Affected versions of this crate did not prevent deep recursion while deserializing data structures.
This allows an attacker to make a YAML file with deeply nested structures that causes an abort while deserializing it.
The flaw was corrected by checking the recursion depth.
Note: clap 2.33 is not affected by this because it uses yaml-rust in a way that doesn't trigger the vulnerability. More specifically:
clap 2.33
The input to the YAML parser is always trusted - is included at compile time via include_str!.
include_str!
The nesting level is never deep enough to trigger the overflow in practice (at most 5).
See advisory page for additional details.
The text was updated successfully, but these errors were encountered:
Note: not related to the usage here, as we use it at compile time against one of the source file for clap.
Sorry, something went wrong.
No branches or pull requests
yaml-rust
0.3.5
>=0.4.1
Affected versions of this crate did not prevent deep recursion while
deserializing data structures.
This allows an attacker to make a YAML file with deeply nested structures
that causes an abort while deserializing it.
The flaw was corrected by checking the recursion depth.
Note:
clap 2.33
is not affected by this because it usesyaml-rust
in a way that doesn't trigger the vulnerability. More specifically:
The input to the YAML parser is always trusted - is included at compile
time via
include_str!
.The nesting level is never deep enough to trigger the overflow in practice
(at most 5).
See advisory page for additional details.
The text was updated successfully, but these errors were encountered: