CVE-2018-16395: An issue was discovered in the OpenSSL library in Ruby before 2.3.8, 2.4.x before 2.4.5, 2.5.x before 2.5.2, and 2.6.x before 2.6.0-preview3.

Critical CVSS 9.8

CVE id
CVE-2018-16395
Published
Last modified

Affected packages

PackageAffected versionsFixed in
Ruby
Runtimes and servers
>= 2.3.0, <= 2.3.7
>= 2.4.0, <= 2.4.4
>= 2.5.0, <= 2.5.1
after 2.3.7, 2.4.4, 2.5.1

How to fix it

Upgrade Ruby to a release newer than the last affected update of the line you run (2.3.7, 2.4.4, 2.5.1).

ruby --version
  • Install the patched Ruby release of your minor line (rbenv, the ruby image tag) and update .ruby-version.

A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.

Details

An issue was discovered in the OpenSSL library in Ruby before 2.3.8, 2.4.x before 2.4.5, 2.5.x before 2.5.2, and 2.6.x before 2.6.0-preview3. When two OpenSSL::X509::Name objects are compared using ==, depending on the ordering, non-equal objects may return true. When the first argument is one character longer than the second, or the second argument contains a character that is one less than a character in the same position of the first argument, the result of == will be true. This could be leveraged to create an illegitimate certificate that may be accepted as legitimate and then used in signing or encryption operations.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.