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

Add Loofah XSS vulnerability #30

Closed
brynary opened this issue Mar 7, 2013 · 4 comments
Closed

Add Loofah XSS vulnerability #30

brynary opened this issue Mar 7, 2013 · 4 comments
Labels

Comments

@brynary
Copy link
Member

brynary commented Mar 7, 2013

https://groups.google.com/forum/?fromgroups=#!searchin/nokogiri-talk/vulnerability/nokogiri-talk/PZK-KcxC_gE/EmB7DFYGGp8J

@tarcieri
Copy link

tarcieri commented Apr 1, 2013

This doesn't have a "cve:" entry... is that kosher?

@mveytsman
Copy link
Member

No cve Id was assigned for the vuln. The rspec tests now require either a cve or a osvdb id to be present. I don't think we'll encounter advisories that aren't in one of the two places.

On 2013-04-01, at 6:59 PM, Tony Arcieri notifications@github.com wrote:

This doesn't have a "cve:" entry... is that kosher?


Reply to this email directly or view it on GitHub.

@tarcieri
Copy link

tarcieri commented Apr 1, 2013

I've been using CVEs as the canonical ID for http://rubysec.github.com ... is that not going to work?

@mveytsman
Copy link
Member

Yeah that's a problem, right now the canonical ID is one of CVE, OSVDB, which is not ideal. let's switch this discussion to #35

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

No branches or pull requests

3 participants