CVE-2023-0401

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 1.8% (78th 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: 1.8%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A NULL pointer can be dereferenced when signatures are being verified on PKCS7 signed or signedAndEnveloped data. In case the hash algorithm used for the signature is known to the OpenSSL library but the implementation of the hash algorithm is not available the digest initialization will fail. There is a missing check for the return value from the initialization function which later leads to invalid usage of the digest API most likely leading to a crash.

The unavailability of an algorithm can be caused by using FIPS enabled configuration of providers or more commonly by not loading the legacy provider.

PKCS7 data is processed by the SMIME library calls and also by the time stamp (TS) library calls. The TLS implementation in OpenSSL does not call these functions however third party applications would be affected if they call these functions to verify signatures on untrusted data.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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%
Exploitation2% × 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
1.8%
EPSS %ILE
78th
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 (7)

Vendor Advisories for CVE-2023-0401(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibssl3 (3.0.5-2ubuntu2.1) @ kinetic2026-05-25ubuntu
ubuntunodejs-doc (12.22.9~dfsg-1ubuntu3.3) @ jammy2026-05-25ubuntu
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

(14 across 14 ecosystems)
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3—
  • every version up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3—
  • every version up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.0.0 up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.0.0 up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.0.0 up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.0.0 up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.0.0 up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.0.0 up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.0.0 up to 3.0.8-r0: fixed in 3.0.8-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.0.0 up to 3.0.8-r0: fixed in 3.0.8-r0
—
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
openssl-src—
  • 300.0.0 up to 300.0.12: fixed in 300.0.12
—
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.

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-0401?
CVE-2023-0401 is a high vulnerability published on February 8, 2023. A NULL pointer can be dereferenced when signatures are being verified on PKCS7 signed or signedAndEnveloped data. In case the hash algorithm used for the signature is known to the OpenSSL library but the implementation of the hash algorithm is not available the digest initialization will fail.…
When was CVE-2023-0401 disclosed?
CVE-2023-0401 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-0401 actively exploited?
CVE-2023-0401 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.8% probability of exploitation in the next 30 days (78th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-0401?
CVE-2023-0401 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2023-0401?
A fix for CVE-2023-0401 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-0401 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-0401

Explore →

Is Your Infrastructure Affected by CVE-2023-0401?

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

Book a Demo →Browse All CVEs