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

Mention the CVE id in "Ruby 1.9.2-p330 Released" #817

Closed
postmodern opened this issue Sep 9, 2014 · 15 comments
Closed

Mention the CVE id in "Ruby 1.9.2-p330 Released" #817

postmodern opened this issue Sep 9, 2014 · 15 comments
Labels

Comments

@postmodern
Copy link
Member

There is no mention of the CVE id in Ruby 1.9.2-p330 Released.

@zzak
Copy link
Member

zzak commented Sep 9, 2014

Could you please email security@ for these kinds of reports, please? Thank you! <3

@zzak zzak closed this as completed Sep 9, 2014
@postmodern
Copy link
Member Author

@zzak you appear to be the original author of the blog post, but simply forgot to mention the CVE id.

Soon after announcing the End of Life for 1.9.2 (and 1.8.7), a critical security regression was found in 1.9.2.

@postmodern postmodern reopened this Sep 9, 2014
@postmodern
Copy link
Member Author

Emailed security@r-l.o as well.

@JuanitoFatas
Copy link
Member

Original Pull Request: #809
cc @hone

@sorah
Copy link
Member

sorah commented Sep 10, 2014

Um? IMO there's no need to send email on security@... if CVE id already exists.

@zzak This is not existing news post's problem so we can handle this here.

@zzak
Copy link
Member

zzak commented Oct 20, 2014

@postmodern what was the CVE id? can you submit a patch? ;)

@postmodern
Copy link
Member Author

@zzak no one seems to know the CVE id, or if one was even requested.

@postmodern
Copy link
Member Author

What's also weird is the v1_9_2_330 tag is missing from the git mirror.

@zzak
Copy link
Member

zzak commented Jul 12, 2015

@postmodern I dont think a CVE was ever assigned, as this was considered a bugfix.

Sorry for the confusion.

@zzak zzak closed this as completed Jul 12, 2015
@postmodern
Copy link
Member Author

Soon after announcing the End of Life for 1.9.2 (and 1.8.7), a critical security regression was found in 1.9.2.

This bug occurs when parsing a long string is using the URI method decode_www_form_component. This can be reproduced by running the following on vulnerable Rubies:

"Critical security regression" doesn't exactly sound like a bugfix. Could you please have security@ request a CVE from MITRE?

@tarcieri
Copy link

Use CVE-2014-6438

@postmodern
Copy link
Member Author

@tarcieri I can't find any information for CVE-2014-6438? If I can get a confirmed CVE, I'll make a PR to fix the news post.

@tarcieri
Copy link

I just got it assigned about an hour ago at @zzak's request (via oss-security)

@postmodern
Copy link
Member Author

and fixed in Pull Request #1138.

@stevebeattie
Copy link

In the updated announcement it's mentioned:

You can read the original report on the bug tracker: https://bugs.ruby-lang.org/issues/5149#note-4

However, that bug report is private. Unless there's confidential information in the report, can you make it public, please? Thanks!

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

No branches or pull requests

6 participants