Sign inStart freeBook a demo

What is CVE-2015-1855?A medium-severity flaw in Ruby, explained.

Medium severity5 affected products
The short answer

CVE-2015-1855 is a medium-severity flaw (CVSS 5.9) in Ruby from Ruby-Lang, published on 29 November 2019. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 2.8%. If you run an affected version, plan in the vendor’s fix.

Check if it affects you →How to fix it

Published 29 November 2019. Record last updated 30 September 2020. We keep this page's data up to date.

What it does

What is CVE-2015-1855? In plain terms.

It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can change data.

The official description

verify_certificate_identity in the OpenSSL extension in Ruby before 2.0.0 patchlevel 645, 2.1.x before 2.1.6, and 2.2.x before 2.2.2 does not properly validate hostnames, which allows remote attackers to spoof servers via vectors related to (1) multiple wildcards, (1) wildcards in IDNA names, (3) case sensitivity, and (4) non-ASCII characters.

What kind of flaw is it?

  • CWE-20Improper Input Validation
CVSS 3.1 scoreMedium · 5.9

How an attack on it works

Read straight from its severity rating, translated out of the shorthand.

  • Where an attacker can beAnywhere on the internet
  • How hard it is to pull offHard: conditions must line up
  • Login needed firstNo login needed
  • Does someone have to clickNo, nobody has to do anything
  • What an attacker getsCan change data

Severity vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Exploitation

Is CVE-2015-1855 being exploited? Not that we know of.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 2.8%. That can change at any time, which is why we keep watching.

Known to be exploitedNoNot on the list of exploited flaws today
Chance of use in the next 30 days2.8%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Record last updated
How Precursor Intelligence ranks it
46out of 100Medium

CVE-2015-1855 scores 46. Action: Plan remediation.

We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:

  • Evidence it is being exploitedBiggest factor
  • How severe it isStrong factor
  • How widely exposed it isSmaller factor
  • Threat activity around itSmaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.

When CVE-2015-1855 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2015-1855? 5 products.

The published record lists 5 products from 3 vendors. Versions are shown as published: "2.1.0 to before 2.1.6" means from 2.1.0 up to, but not including, 2.1.6. If you run one of these, check your version, then go to the fix below.

  • Application

    Ruby

    by Ruby-Lang

    Affected versions
    2.0.02.0.0-p02.0.0-p1952.0.0-p2472.0.0-p3532.0.0-p4512.0.0-p4812.0.0-p5762.0.0-p5942.0.0-p5982.0.0-p6432.1.0 to before 2.1.62.2.0 to before 2.2.2
  • Operating system

    Debian Linux

    by Debian

    Affected versions
    7.08.09.0
  • Application

    Puppet Agent

    by Puppet

    Affected versions
    1.0.0
  • Application

    Puppet Enterprise

    by Puppet

    Affected versions
    3.0.0 to before 3.8.0
  • Application

    Trunk

    by Ruby-Lang

    Affected versions
    before 50292
Remediation

How do I fix CVE-2015-1855? Four steps.

  1. Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
  2. Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
  3. If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
  4. Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

References

6 links
Precursor Intelligence

Does CVE-2015-1855 affect you? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2015-1855 is a medium-severity flaw in Ruby from Ruby-Lang, published on 29 November 2019. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can change data.

It scores 5.9 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2015-1855 is 46 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 2.8%. That can change at any time, which is why we keep watching.

For Ruby from Ruby-Lang: 2.0.0, 2.0.0-p0, 2.0.0-p195, 2.0.0-p247, 2.0.0-p353, 2.0.0-p451 and 7 more. The record lists 5 products in all, each with its versions, under "Who is affected" on this page.

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

Keep exploring