CVE-2023-0215

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 4.5% (91st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications.

The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash.

This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7.

Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream.

The OpenSSL cms and smime command line applications are similarly affected.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
51
EG Risk 51/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation4% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
4.5%
EPSS %ILE
91st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

February 8, 2023

Last Modified

November 4, 2025

References (17)

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibssl3 (3.0.5-2ubuntu2.1) @ kinetic2026-05-25ubuntu
ubuntulibssl1.0-dev (1.0.2n-1ubuntu5.11) @ bionic2026-05-25ubuntu
ubuntuqemu-efi-riscv64 (2025.02-3ubuntu2.2) @ plucky2026-05-25ubuntu
ubuntulibssl1.0.0 (1.0.1f-1ubuntu2.27+esm6) @ trusty2026-05-25ubuntu
ubuntunodejs-doc (12.22.9~dfsg-1ubuntu3.3) @ jammy2026-05-25ubuntu
redhatedk2-0:20220126gitbb1bba3d77-2.el8_6.12023-07-18redhat
redhatopenssl2023-06-05redhat
redhatjws5-tomcat-native-0:1.2.31-14.redhat_14.el9jws2023-06-05redhat
redhatjbcs-httpd24-openssl-1:1.1.1k-14.el7jbcs2023-06-05redhat
redhatopenssl-1:1.1.1k-9.el8_62023-05-31redhat
redhatedk2-0:20220126gitbb1bba3d77-4.el82023-05-16redhat
redhatedk2-0:20221207gitfff6d81270b5-9.el9_22023-05-09redhat
redhatopenssl-1:1.1.1k-9.el8_72023-03-22redhat
redhatopenssl-1:3.0.1-46.el9_02023-03-14redhat
redhatopenssl-1:3.0.1-47.el9_12023-02-28redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(19 across 17 ecosystems)
Alpine:v3.15(2)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1t-r0: fixed in 1.1.1t-r0
—
openssl3—
  • every version up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.16(2)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1t-r0: fixed in 1.1.1t-r0
—
openssl3—
  • every version up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1t-r0: fixed in 1.1.1t-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.0.8-r0: fixed in 3.0.8-r0
—
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
openssl-src—
  • every version up to 111.25.0: fixed in 111.25.0
  • 300.0.0 up to 300.0.12: fixed in 300.0.12
  • 0.0.0-0 up to 111.25.0: fixed in 111.25.0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
openssl1.1.1c-1 ... 1.1.1n-0+deb10u3 (25 versions)
  • every version up to 1.1.1n-0+deb10u4: fixed in 1.1.1n-0+deb10u4
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
openssl1.1.1k-1 ... 1.1.1n-0+deb11u3 (9 versions)
  • every version up to 1.1.1n-0+deb11u4: fixed in 1.1.1n-0+deb11u4
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 3.0.8-1: fixed in 3.0.8-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 3.0.8-1: fixed in 3.0.8-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 3.0.8-1: fixed in 3.0.8-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 6× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 170 total refreshes for this CVE.

  1. 2026-10-09 20:05 UTCEPSS rescore
  2. 2026-10-08 17:05 UTCEPSS rescore
  3. 2026-10-07 23:45 UTCEPSS rescore
  4. 2026-10-06 15:14 UTCEPSS rescore
  5. 2026-10-05 17:40 UTCEPSS rescore
  6. 2026-10-03 14:23 UTCEPSS rescore
  7. 2026-09-30 16:13 UTCEG score recompute
  8. 2026-09-30 15:01 UTCEPSS rescore
  9. 2026-09-27 13:42 UTCEPSS rescore
  10. 2026-09-26 15:55 UTCEPSS rescore
  11. 2026-09-26 00:22 UTCEPSS rescore
  12. 2026-09-24 14:00 UTCEPSS rescore
  13. 2026-09-23 20:41 UTCOSV refresh
  14. 2026-09-23 13:45 UTCEPSS rescore
  15. 2026-09-20 20:13 UTCEPSS rescore
  16. 2026-09-16 14:05 UTCEPSS rescore
  17. 2026-09-16 05:11 UTCEPSS rescore
  18. 2026-09-15 03:07 UTCEPSS rescore
  19. 2026-09-11 14:50 UTCEPSS rescore
  20. 2026-09-11 09:34 UTCEPSS rescore
  21. 2026-09-08 21:57 UTCEPSS rescore
  22. 2026-09-07 15:59 UTCEPSS rescore
  23. 2026-09-06 13:45 UTCEPSS rescore
  24. 2026-09-05 15:25 UTCEPSS rescore
  25. 2026-09-04 15:54 UTCOSV refresh
Show 75 more
  1. 2026-09-04 13:57 UTCEPSS rescore
  2. 2026-09-04 05:04 UTCEPSS rescore
  3. 2026-09-02 14:09 UTCEPSS rescore
  4. 2026-09-01 13:51 UTCEPSS rescore
  5. 2026-08-30 19:15 UTCEPSS rescore
  6. 2026-08-30 01:19 UTCEPSS rescore
  7. 2026-08-28 21:38 UTCEPSS rescore
  8. 2026-08-27 14:22 UTCEPSS rescore
  9. 2026-08-26 14:43 UTCEPSS rescore
  10. 2026-08-25 13:46 UTCEPSS rescore
  11. 2026-08-23 00:17 UTCEPSS rescore
  12. 2026-08-21 23:46 UTCEPSS rescore
  13. 2026-08-20 22:53 UTCEPSS rescore
  14. 2026-08-19 17:01 UTCEPSS rescore
  15. 2026-08-18 13:45 UTCEPSS rescore
  16. 2026-08-18 03:04 UTCOSV refresh
  17. 2026-08-17 13:44 UTCEPSS rescore
  18. 2026-08-16 14:53 UTCEPSS rescore
  19. 2026-08-16 02:12 UTCEPSS rescore
  20. 2026-08-15 01:27 UTCEPSS rescore
  21. 2026-08-13 21:58 UTCEPSS rescore
  22. 2026-08-12 13:48 UTCEPSS rescore
  23. 2026-08-09 13:44 UTCEPSS rescore
  24. 2026-08-09 13:44 UTCEPSS rescore
  25. 2026-08-08 16:34 UTCEPSS rescore
  26. 2026-08-07 16:24 UTCEPSS rescore
  27. 2026-08-06 13:44 UTCEPSS rescore
  28. 2026-08-05 19:15 UTCEPSS rescore
  29. 2026-08-04 15:07 UTCEPSS rescore
  30. 2026-08-04 10:35 UTCEPSS rescore
  31. 2026-08-03 10:33 UTCEPSS rescore
  32. 2026-08-02 21:57 UTCOSV refresh
  33. 2026-08-02 02:24 UTCEPSS rescore
  34. 2026-08-01 04:13 UTCEPSS rescore
  35. 2026-08-01 04:13 UTCEPSS rescore
  36. 2026-07-30 16:25 UTCEPSS rescore
  37. 2026-07-30 01:28 UTCEPSS rescore
  38. 2026-07-28 15:34 UTCEPSS rescore
  39. 2026-07-25 14:16 UTCEPSS rescore
  40. 2026-07-24 14:15 UTCEPSS rescore
  41. 2026-07-23 14:16 UTCEPSS rescore
  42. 2026-07-23 14:16 UTCEPSS rescore
  43. 2026-07-23 02:17 UTCEG score recompute
  44. 2026-07-22 23:04 UTCEG score recompute
  45. 2026-07-22 14:06 UTCEPSS rescore
  46. 2026-07-22 14:06 UTCEPSS rescore
  47. 2026-07-21 15:23 UTCEPSS rescore
  48. 2026-07-21 15:23 UTCEPSS rescore
  49. 2026-07-20 17:05 UTCEPSS rescore
  50. 2026-07-19 14:29 UTCEPSS rescore
  51. 2026-07-19 14:29 UTCEPSS rescore
  52. 2026-07-19 02:27 UTCEPSS rescore
  53. 2026-07-19 02:27 UTCEPSS rescore
  54. 2026-07-18 10:03 UTCEPSS rescore
  55. 2026-07-18 10:03 UTCEPSS rescore
  56. 2026-07-16 17:00 UTCEPSS rescore
  57. 2026-07-16 06:49 UTCOSV refresh
  58. 2026-07-15 16:56 UTCEPSS rescore
  59. 2026-07-15 16:56 UTCEPSS rescore
  60. 2026-07-15 01:58 UTCEPSS rescore
  61. 2026-07-15 01:58 UTCEPSS rescore
  62. 2026-07-13 22:28 UTCEPSS rescore
  63. 2026-07-13 22:28 UTCEPSS rescore
  64. 2026-07-13 06:11 UTCEPSS rescore
  65. 2026-07-13 06:11 UTCEPSS rescore
  66. 2026-07-12 05:44 UTCEPSS rescore
  67. 2026-07-11 08:25 UTCEPSS rescore
  68. 2026-07-11 08:25 UTCEPSS rescore
  69. 2026-07-09 19:08 UTCEPSS rescore
  70. 2026-07-08 15:13 UTCEPSS rescore
  71. 2026-07-07 13:44 UTCEPSS rescore
  72. 2026-07-06 16:25 UTCEPSS rescore
  73. 2026-07-06 02:21 UTCEPSS rescore
  74. 2026-07-05 02:28 UTCEPSS rescore
  75. 2026-07-04 06:29 UTCEPSS rescore

Frequently asked(5)

What is CVE-2023-0215?
CVE-2023-0215 is a high vulnerability published on February 8, 2023. The public API function BIOnewNDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications. The function receives a BIO from the…
When was CVE-2023-0215 disclosed?
CVE-2023-0215 was first published on February 8, 2023, with the most recent update on November 4, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-0215 actively exploited?
CVE-2023-0215 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.5% probability of exploitation in the next 30 days (91st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-0215?
CVE-2023-0215 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2023-0215?
A fix for CVE-2023-0215 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-0215 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-0215

Explore →

Is Your Infrastructure Affected by CVE-2023-0215?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.