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 New Ruby-Saml vulnerability #163

Closed
wants to merge 8 commits into from
Closed

Add New Ruby-Saml vulnerability #163

wants to merge 8 commits into from

Conversation

VanessaHenderson
Copy link
Contributor

This ruby-saml vuln came through the mailing lists this morning. Its not on OSVDB as far as I can tell (and I can't figure out how to create one) but a CVE was requested so for now I just put the date as the file name.

A second Ruby advisory with the same story, CVE request but not OSVDB
was sent out today as well. Added that. The CVSS_2 scores were
calculated by a colleague
@phillmv
Copy link
Member

phillmv commented Jul 9, 2015

CVEs are usually pretty quick on the uptake. Why not wait until later on/tomorrow?

@VanessaHenderson
Copy link
Contributor Author

Okay, I'll see if they respond by tomorrow, I'll just let this sit in a PR until then :)

@phillmv
Copy link
Member

phillmv commented Jul 9, 2015

👍 thanks Vanessa!

@postmodern
Copy link
Member

I will also adjust the specs to allow missing CVEs.

@VanessaHenderson
Copy link
Contributor Author

What should the file names be in the case that there is no CVE/OSVDB? dates will get tedious, not that I'm expecting there to be many of these

@postmodern
Copy link
Member

Ah, I see now, it's missing both CVE and OSVDB. Also email moderators@osvdb.org and see who assigns an ID first.

@postmodern
Copy link
Member

That's a good question. Generally either MITRE or OSVDB would quickly assign an ID.

@phillmv
Copy link
Member

phillmv commented Jul 9, 2015

So far the way we've been setup requires one or the other - and lately we've been preferring CVEs.

@reedloden
Copy link
Member

I was the one who put in the requests to MITRE / oss-security and OSVDB... OSVDB got back to me and said they are experiencing infrastructure problems and aren't sure when they will be able to assign IDs again. MITRE takes forever for CVE requests.

As soon as I have an update, I'll let you know.

@reedloden
Copy link
Member

OSVDB has assigned the XEE vuln (SAML-Toolkits/ruby-saml#247) as OSVDB-124383, though it won't show up on the site until they fix some problems. At least this unblocks us from getting this added. Still waiting for the assignment for the other vuln.

@VanessaHenderson
Copy link
Contributor Author

I've added that one in there @reedloden :)

@reedloden
Copy link
Member

and OSVDB has assigned the XPath injection (SAML-Toolkits/ruby-saml#225) as OSVDB-124991.

title: Ruby-Saml Gem is vulnerable to XPath Injection
date: 2015-07-09
description: |
ruby-saml before 1.0.0 is vulnerable to XPath injection on xml_security.rb. The lack of prepared statements allows for possibly command injection, leading to arbitrary code execution
Copy link
Member

Choose a reason for hiding this comment

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

Can you wrap at 80 chars here?

@reedloden
Copy link
Member

I think once you update 07092015_2 to reference OSVDB-124991 instead, this should be good to go.

@VanessaHenderson
Copy link
Contributor Author

I was in the process of doing that!

osvdb: 124991
url: https://github.com/onelogin/ruby-saml/pull/225
title: Ruby-Saml Gem is vulnerable to XPath Injection
date: 2015-07-09
Copy link
Member

Choose a reason for hiding this comment

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

Let's make this 2015-04-29, as that's when SAML-Toolkits/ruby-saml@9853651 was committed.

@reedloden
Copy link
Member

Awesome. Let's get the dates changed and squash your commits into one, and this should be good to go. :)

Yay more date changes
@reedloden
Copy link
Member

Can you squash your commits into one (or one for each)? That's the only thing I see outstanding...

@postmodern
Copy link
Member

👍 I'll squash it for you.

@postmodern
Copy link
Member

Merged by hand in d9ec6d2. Thank you for being patient!

@postmodern postmodern closed this Jul 21, 2015
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.

4 participants