Skip to content
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

Prevent too deep recursion #109

Merged
merged 2 commits into from
Sep 15, 2018

Conversation

KamilaBorowska
Copy link
Contributor

No description provided.

Copy link
Collaborator

@dtolnay dtolnay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@dtolnay dtolnay force-pushed the prevent-too-deep-recursion branch from 644ee83 to 35ca228 Compare September 15, 2018 16:18
@dtolnay dtolnay merged commit 7eb6b6a into chyh1990:master Sep 15, 2018
@Shnatsel
Copy link

Shnatsel commented Jan 5, 2019

Is it possible to backport this to 0.3.x series? According to crates.io stats, half of the recent downloads of rust-yaml are in the 0.3.x.

If this fix is already backported, please let me know and I'll update the security advisory.

@KamilaBorowska
Copy link
Contributor Author

@Shnatsel Most of the rust-yaml downloads are due to clap, which isn't really affected by this issue, making this mostly unimportant.

@Shnatsel
Copy link

Shnatsel commented Jan 6, 2019

There is a total of 165 crates on crates.io currently affected without a semver-compatible upgrade path, according to crates-audit. So it might not be as unimportant as it seems.

@Shnatsel
Copy link

Shnatsel commented Jan 6, 2019

Here's the list of affected crates, without crates depending on clap, sorted by recent download count: https://ncry.pt/p/vzOn#8UqV4ktfnn67-ReSMfvj-xjFZQq1wdDh3uUzK8AhxBk
That's 51 crates, nothing really critical at the top of the list as far as I can tell.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants