Skip to content

Ruby Openssl Allows Incorrect Value Comparison

Critical severity GitHub Reviewed Published May 13, 2022 to the GitHub Advisory Database • Updated Jul 24, 2023

Package

bundler openssl (RubyGems)

Affected versions

< 2.0.9
>= 2.1.0, < 2.1.2

Patched versions

2.0.9
2.1.2

Description

An issue was discovered in the OpenSSL library in Ruby 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

Published by the National Vulnerability Database Nov 16, 2018
Published to the GitHub Advisory Database May 13, 2022
Reviewed Jun 9, 2023
Last updated Jul 24, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.903%
(83rd percentile)

Weaknesses

No CWEs

CVE ID

CVE-2018-16395

GHSA ID

GHSA-mmrq-6999-72v8

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.