CVE-2019-1559

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

Score 5.9 from GitHub Security Advisory published 2022-05-13. NVD baseline CVSS 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 17%CVSS: 5.9Exploit: Elevated riskExposed: 0

A fix is available — apply it.

If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a close_notify, and once to receive one) then OpenSSL can respond differently to the calling application if a 0 byte record is received with invalid padding compared to if a 0 byte record is received with an invalid MAC. If the application then behaves differently based on that in a way that is detectable to the remote peer, then this amounts to a padding oracle that could be used to decrypt data. In order for this to be exploitable "non-stitched" ciphersuites must be in use. Stitched ciphersuites are optimised implementations of certain commonly used ciphersuites. Also the application must call SSL_shutdown() twice even if a protocol error has occurred (applications should not do this but some do anyway). Fixed in OpenSSL 1.0.2r (Affected 1.0.2-1.0.2q).

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
47(Track)
EG Risk 47/100SSVC: Track

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
Severity59% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
17%
EPSS %ILE
97%
KEV
Not listed

Published

February 27, 2019

Last Modified

November 21, 2024

References (72)

Vendor Advisories for CVE-2019-1559(1)

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl (1.0.2g-1ubuntu4.15) @ xenial2026-05-27ubuntu
ubuntulibssl1.0.0-udeb (1.0.1f-1ubuntu2.27+esm1) @ trusty2026-05-27ubuntu
redhatansible-tower-37/ansible-tower-memcached-rhel7:1.4.15-282020-02-18redhat
redhatopenssl2019-11-20redhat
redhatjws5-tomcat-vault-0:1.1.8-1.Final_redhat_1.1.el8jws2019-11-20redhat
redhatopenssl-0:1.0.1e-58.el6_102019-08-13redhat
redhatredhat-virtualization-host-0:4.3.5-20190722.0.el7_72019-08-12redhat
redhatrhvm-appliance-0:4.3-20190722.0.el72019-08-12redhat
redhatopenssl-1:1.0.2k-19.el72019-08-06redhat

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

(9 across 9 ecosystems)
Alpine:v3.6(1)
PackageVulnerable rangeFixed inDependents
openssl—1.0.2r-r0—
Alpine:v3.7(1)
PackageVulnerable rangeFixed inDependents
openssl—1.0.2r-r0—
Alpine:v3.8(1)
PackageVulnerable rangeFixed inDependents
openssl—1.0.2r-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
openssl—1.1.0b-2—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssl—1.1.0b-2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl—1.1.0b-2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl—1.1.0b-2—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
openssl1.0.1k-3 ... 1.0.1t-1+deb8u9 (17 versions)1.0.1t-1+deb8u11—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
openssl1.01.0.2l-2 ... 1.0.2q-2 (14 versions)1.0.2r-1~deb9u1—

Weakness Classification(1)

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

Additional Vendor Advisories

(8)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 24× 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 136 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-1559?
CVE-2019-1559 is a medium vulnerability published on February 27, 2019. If an application encounters a fatal protocol error and then calls SSLshutdown() twice (once to send a closenotify, and once to receive one) then OpenSSL can respond differently to the calling application if a 0 byte record is received with invalid padding compared to if a 0 byte record is received…
When was CVE-2019-1559 disclosed?
CVE-2019-1559 was first published in the National Vulnerability Database on February 27, 2019, 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-2019-1559 actively exploited?
CVE-2019-1559 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17% probability of exploitation in the next 30 days, which ranks it in the top 3.1% of all scored CVEs.
What is the CVSS score of CVE-2019-1559?
CVE-2019-1559 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2019-1559?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-1559, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-1559

Explore →

Is Your Infrastructure Affected by CVE-2019-1559?

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

Start Free Scan →Browse All CVEs