CVE-2019-1543

HIGHNVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 5.7%CVSS: 7.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any additional leading bytes are ignored. It is a requirement of using this cipher that nonce values are unique. Messages encrypted using a reused nonce value are susceptible to serious confidentiality and integrity attacks. If an application changes the default nonce length to be longer than 12 bytes and then makes a change to the leading bytes of the nonce expecting the new value to be a new unique nonce then such an application could inadvertently encrypt messages with a reused nonce. Additionally the ignored bytes in a long nonce are not covered by the integrity guarantee of this cipher. Any application that relies on the integrity of these ignored leading bytes of a long nonce may be further affected. Any OpenSSL internal use of this cipher, including in SSL/TLS, is safe because no such use sets such a long nonce value. However user applications that use this cipher directly and set a non-default nonce length to be longer than 12 bytes may be vulnerable. OpenSSL versions 1.1.1 and 1.1.0 are affected by this issue. Due to the limited scope of affected deployments this has been assessed as low severity and therefore we are not creating new releases at this time. Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b). Fixed in OpenSSL 1.1.0k (Affected 1.1.0-1.1.0j).

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
40
EG Risk 40/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
Severity74% × 45%
Exploitation6% × 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
5.7%
EPSS %ILE
92nd
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 none (no KEV listing, exploit record or EPSS ≥ 50%) · 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

March 6, 2019

Last Modified

November 21, 2024

References (26)

Vendor Advisories for CVE-2019-1543(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenssl-1:1.1.1c-2.el82019-11-05redhat

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

(38 across 21 ecosystems)
Alpine:v3.15(3)
PackageVulnerable rangeFix by version rangeDependents
file—
  • every version up to 5.36-r0: fixed in 5.36-r0
—
openssl—
  • 1.1.0 up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
openssl3—
  • every version up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
Alpine:v3.16(3)
PackageVulnerable rangeFix by version rangeDependents
file—
  • every version up to 5.36-r0: fixed in 5.36-r0
—
openssl—
  • 1.1.0 up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
openssl3—
  • every version up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
Alpine:v3.10(2)
PackageVulnerable rangeFix by version rangeDependents
file—
  • every version up to 5.36-r0: fixed in 5.36-r0
—
openssl—
  • 1.1.0 up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
Alpine:v3.11(2)
PackageVulnerable rangeFix by version rangeDependents
file—
  • every version up to 5.36-r0: fixed in 5.36-r0
—
openssl—
  • 1.1.0 up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
Alpine:v3.12(2)
PackageVulnerable rangeFix by version rangeDependents
file—
  • every version up to 5.36-r0: fixed in 5.36-r0
—
openssl—
  • 1.1.0 up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
Alpine:v3.13(2)
PackageVulnerable rangeFix by version rangeDependents
file—
  • every version up to 5.36-r0: fixed in 5.36-r0
—
openssl—
  • 1.1.0 up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
Alpine:v3.14(2)
PackageVulnerable rangeFix by version rangeDependents
file—
  • every version up to 5.36-r0: fixed in 5.36-r0
—
openssl—
  • 1.1.0 up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
Alpine:v3.17(2)
PackageVulnerable rangeFix by version rangeDependents
file—
  • every version up to 5.36-r0: fixed in 5.36-r0
—
openssl—
  • 1.1.0 up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
Alpine:v3.18(2)
PackageVulnerable rangeFix by version rangeDependents
file—
  • every version up to 5.36-r0: fixed in 5.36-r0
—
openssl—
  • 1.1.0 up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
Alpine:v3.19(2)
PackageVulnerable rangeFix by version rangeDependents
file—
  • every version up to 5.36-r0: fixed in 5.36-r0
—
openssl—
  • 1.1.0 up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
Alpine:v3.20(2)
PackageVulnerable rangeFix by version rangeDependents
file—
  • every version up to 5.36-r0: fixed in 5.36-r0
—
openssl—
  • 1.1.0 up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
Alpine:v3.21(2)
PackageVulnerable rangeFix by version rangeDependents
file—
  • every version up to 5.36-r0: fixed in 5.36-r0
—
openssl—
  • 1.1.0 up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
Alpine:v3.22(2)
PackageVulnerable rangeFix by version rangeDependents
file—
  • every version up to 5.36-r0: fixed in 5.36-r0
—
openssl—
  • 1.1.0 up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
Alpine:v3.23(2)
PackageVulnerable rangeFix by version rangeDependents
file—
  • every version up to 5.36-r0: fixed in 5.36-r0
—
openssl—
  • 1.1.0 up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
Alpine:v3.24(2)
PackageVulnerable rangeFix by version rangeDependents
file—
  • every version up to 5.36-r0: fixed in 5.36-r0
—
openssl—
  • 1.1.0 up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.1.0 up to 1.1.1b-r1: fixed in 1.1.1b-r1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1c-1: fixed in 1.1.1c-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1c-1: fixed in 1.1.1c-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1c-1: fixed in 1.1.1c-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1c-1: fixed in 1.1.1c-1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
openssl1.1.0f-3 ... 1.1.0j-1~deb9u1 (13 versions)
  • every version up to 1.1.0k-1~deb9u1: fixed in 1.1.0k-1~deb9u1
—

Weakness Classification(2)

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

All Vendor Advisories

(1)

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 6× in last 7d / 28× 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 161 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2019-1543?
CVE-2019-1543 is a high vulnerability published on March 6, 2019. ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also…
When was CVE-2019-1543 disclosed?
CVE-2019-1543 was first published on March 6, 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-1543 actively exploited?
CVE-2019-1543 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.7% probability of exploitation in the next 30 days (92nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-1543?
CVE-2019-1543 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2019-1543?
A fix for CVE-2019-1543 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-1543 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-2019-1543

Explore →

Is Your Infrastructure Affected by CVE-2019-1543?

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