CVE-2018-11056 json
RSA BSAFE Micro Edition Suite, prior to 4.1.6.1 (in 4.1.x), and RSA BSAFE Crypto-C Micro Edition versions prior to 4.0.5.3 (in 4.0.x) conta…
published 2018-08-31 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-3100
- cvss
- 6.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
RSA BSAFE Micro Edition Suite, prior to 4.1.6.1 (in 4.1.x), and RSA BSAFE Crypto-C Micro Edition versions prior to 4.0.5.3 (in 4.0.x) contain an Uncontrolled Resource Consumption ('Resource Exhaustion') vulnerability when parsing ASN.1 data. A remote attacker could use maliciously constructed ASN.1 data that would exhaust the stack, potentially causing a Denial Of Service.
Patch / fix
- RSA BSAFE Micro Edition Suite 4.1.6.1
- RSA BSAFE Crypto-C Micro Edition 4.0.5.3
Exploit prediction
1.87% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:N/A:P |
Affected products
- RSA BSAFE Micro Edition Suite
- RSA BSAFE Crypto-C Micro Edition
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
oracle.com
/security-alerts/cpuapr2020.html
patch, third-party-advisory
-
oracle.com
/security-alerts/cpujul2020.html
patch, third-party-advisory
-
oracle.com
/technetwork/security-advisory/cpujul2019-5072835.html
patch, third-party-advisory
-
oracle.com
/security-alerts/cpujan2020.html
patch, third-party-advisory
-
oracle.com
/security-alerts/cpuoct2020.html
patch, third-party-advisory
-
seclists.org
/fulldisclosure/2018/Aug/46
mailing-list, third-party-advisory
Sources
- CVE List CVE-2018-11056
- NVD CVE-2018-11056
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.