CVE-2021-4044

HIGHNVD 7.58.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.0 because EPSS predicts 50% probability of exploitation within the next 30 days (98th percentile of EPSS-scored CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, nvd
Elevated
8.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 50%
CISA-KEV: Not listedEPSS PROB: 50%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Internally libssl in OpenSSL calls X509_verify_cert() on the client side to verify a certificate supplied by a server. That function may return a negative return value to indicate an internal error (for example out of memory). Such a negative return value is mishandled by OpenSSL and will cause an IO function (such as SSL_connect() or SSL_do_handshake()) to not indicate success and a subsequent call to SSL_get_error() to return the value SSL_ERROR_WANT_RETRY_VERIFY. This return value is only supposed to be returned by OpenSSL if the application has previously called SSL_CTX_set_cert_verify_callback(). Since most applications do not do this the SSL_ERROR_WANT_RETRY_VERIFY return value from SSL_get_error() will be totally unexpected and applications may not behave correctly as a result. The exact behaviour will depend on the application but it could result in crashes, infinite loops or other similar incorrect responses. This issue is made more serious in combination with a separate bug in OpenSSL 3.0 that will cause X509_verify_cert() to indicate an internal error when processing a certificate chain. This will occur where a certificate does not include the Subject Alternative Name extension but where a Certificate Authority has enforced name constraints. This issue can occur even with valid chains. By combining the two issues an attacker could induce incorrect, application dependent behaviour. Fixed in OpenSSL 3.0.1 (Affected 3.0.0).

CVSS v3
7.5
EG Score
8.0HIGHhigh confidence
EG Risk
61
EG Risk 61/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
Severity80% × 45%
Exploitation50% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or 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
50%
EPSS %ILE
98th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or 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 public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). 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

December 14, 2021

Last Modified

November 21, 2024

Affected Packages

(11 across 11 ecosystems)
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3—
  • every version up to 3.0.2-r0: fixed in 3.0.2-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3—
  • every version up to 3.0.1-r0: fixed in 3.0.1-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 3.0.1-r0: fixed in 3.0.1-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 3.0.1-r0: fixed in 3.0.1-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 3.0.1-r0: fixed in 3.0.1-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 3.0.1-r0: fixed in 3.0.1-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 3.0.1-r0: fixed in 3.0.1-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 3.0.1-r0: fixed in 3.0.1-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 3.0.1-r0: fixed in 3.0.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 3.0.1-r0: fixed in 3.0.1-r0
—
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
openssl-src—
  • 300.0.0 up to 300.0.4: fixed in 300.0.4
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 26× 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 142 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2021-4044?
CVE-2021-4044 is a high vulnerability published on December 14, 2021. Internally libssl in OpenSSL calls X509verifycert() on the client side to verify a certificate supplied by a server. That function may return a negative return value to indicate an internal error (for example out of memory). Such a negative return value is mishandled by OpenSSL and will cause an IO…
When was CVE-2021-4044 disclosed?
CVE-2021-4044 was first published on December 14, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-4044 actively exploited?
CVE-2021-4044 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 50% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-4044?
CVE-2021-4044 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.0 (HIGH).
How do I remediate CVE-2021-4044?
A fix for CVE-2021-4044 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-4044

Explore →

Is Your Infrastructure Affected by CVE-2021-4044?

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