Exponent Openswan up to 2.6.50.0 IKEv2 Signature RSA Signature Bleichenbacher signature verification

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.2$0-$5k0.00

A vulnerability, which was classified as critical, has been found in Exponent Openswan up to 2.6.50.0. This issue affects an unknown function of the component IKEv2 Signature Handler. The manipulation as part of a RSA Signature leads to a signature verification vulnerability (Bleichenbacher). Using CWE to declare the problem leads to CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

In Openswan before 2.6.50.1, IKEv2 signature verification is vulnerable to "Variants of Bleichenbacher's Low-Exponent Attack on PKCS#1 RSA Signatures" attacks when RAW RSA keys are used.

The bug was discovered 08/25/2018. The weakness was released 09/26/2018 (Website). The advisory is shared at lists.openswan.org. The identification of this vulnerability is CVE-2018-15836 since 08/23/2018. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.

The vulnerability was handled as a non-public zero-day exploit for at least 32 days. During that time the estimated underground price was around $0-$5k.

Upgrading to version bis 2.6.50.0 eliminates this vulnerability.

Productinfo

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB CVSS-B Score: 🔍
VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.4
VulDB Meta Temp Score: 7.2

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Name: Bleichenbacher
Class: Signature verification / Bleichenbacher
CWE: CWE-347 / CWE-345
CAPEC: 🔍
ATT&CK: 🔍

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Openswan bis 2.6.50.0
Patch: github.com

Timelineinfo

08/23/2018 🔍
08/25/2018 +2 days 🔍
09/26/2018 +31 days 🔍
09/26/2018 +0 days 🔍
09/27/2018 +1 days 🔍
05/19/2023 +1695 days 🔍

Sourcesinfo

Advisory: 0b460be9e287fd335c8ce58129c67bf06065ef51
Status: Not defined
Confirmation: 🔍

CVE: CVE-2018-15836 (🔍)

Entryinfo

Created: 09/27/2018 08:58
Updated: 05/19/2023 08:43
Changes: 09/27/2018 08:58 (62), 04/25/2020 16:52 (1), 05/19/2023 08:43 (5)
Complete: 🔍

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!