CVE-2019-1543: ChaCha20-Poly1305 with long nonces
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 5.7% (FIRST EPSS); higher than 93% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: file (Alpine:v3.10) 5.36-r0; openssl (Alpine:v3.10) 1.1.1b-r1; openssl3 (Alpine:v3.15) 1.1.1b-r1.
Low priority for now. Upgrade to file (Alpine:v3.10) 5.36-r0; openssl (Alpine:v3.10) 1.1.1b-r1; openssl3 (Alpine:v3.15) 1.1.1b-r1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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).
- Published
- Mar 6, 2019
- Updated
- Jun 16, 2026
- EPSS
- 5.7% · 93th percentile
- CWE
- CWE-327
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 29 / 40 · 7.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 5.7%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openssl | openssl | cpe:2.3:a:openssl:openssl |
Check your server's TLS configuration
The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- openssl openssl1.1.0 and later · up to 1.1.0j inclusive
- openssl openssl1.1.1 and later · up to 1.1.1b inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.
OpenSSL OpenSSL
- 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)affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | file | before 5.36-r0 | 5.36-r0 |
| Alpine:v3.10 | openssl | from 1.1.0 · before 1.1.1b-r1 | 1.1.1b-r1 |
| Alpine:v3.15 | openssl3 | before 1.1.1b-r1 | 1.1.1b-r1 |
| Debian:12 | openssl | before 1.1.1c-1 | 1.1.1c-1 |
| Debian:9 | openssl | before 1.1.0k-1~deb9u1 | 1.1.0k-1~deb9u1 |
| openSUSE:Leap 15.0 | openssl-1_1 | before 1.1.0i-lp150.3.22.3 | 1.1.0i-lp150.3.22.3 |
| openSUSE:Leap 15.0 | virtualbox | before 6.0.10-lp151.2.6.1 | 6.0.10-lp151.2.6.1 |
| Red Hat:enterprise_linux:8::baseos | openssl | before 1:1.1.1c-2.el8 | 1:1.1.1c-2.el8 |
| Red Hat:enterprise_linux:8::baseos | openssl-debuginfo | before 1:1.1.1c-2.el8 | 1:1.1.1c-2.el8 |
| Red Hat:enterprise_linux:8::baseos | openssl-debugsource | before 1:1.1.1c-2.el8 | 1:1.1.1c-2.el8 |
| Red Hat:enterprise_linux:8::baseos | openssl-devel | before 1:1.1.1c-2.el8 | 1:1.1.1c-2.el8 |
| Red Hat:enterprise_linux:8::baseos | openssl-libs | before 1:1.1.1c-2.el8 | 1:1.1.1c-2.el8 |
| Red Hat:enterprise_linux:8::baseos | openssl-libs-debuginfo | before 1:1.1.1c-2.el8 | 1:1.1.1c-2.el8 |
| Red Hat:enterprise_linux:8::baseos | openssl-perl | before 1:1.1.1c-2.el8 | 1:1.1.1c-2.el8 |
| SUSE:Linux Enterprise Desktop 12 SP4 | openssl-1_1 | before 1.1.1-2.9.1 | 1.1.1-2.9.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 | openssl-1_1 | before 1.1.0i-4.21.1 | 1.1.0i-4.21.1 |
Same product
openssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV90Now
- CVE-2021-3711SM2 Decryption Buffer Overflow65This week
- CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code 65This week
Published before and after this one in the same product
- ← EarlierCVE-2018-0734Oct 30, 2018 · Timing attack against DSA27Monitor
- ← EarlierCVE-2019-1559Feb 27, 2019 · 0-byte record padding oracle28Monitor
- Later →CVE-2019-1552Jul 30, 2019 · Windows builds with insecure path defaults13Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:file | 5.36-r0 · Alpine:v3.10 | Package registry (OSV) |
| alpine:openssl | 1.1.1b-r1 · Alpine:v3.10 | Package registry (OSV) |
| alpine:openssl3 | 1.1.1b-r1 · Alpine:v3.15 | Package registry (OSV) |
| debian:openssl | 1.1.1c-1 · Debian:12 | Package registry (OSV) |
| opensuse:openssl-1_1 | 1.1.0i-lp150.3.22.3 · openSUSE:Leap 15.0 | Package registry (OSV) |
| opensuse:virtualbox | 6.0.10-lp151.2.6.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| red hat:openssl | 1:1.1.1c-2.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:openssl-debuginfo | 1:1.1.1c-2.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:openssl-debugsource | 1:1.1.1c-2.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:openssl-devel | 1:1.1.1c-2.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:openssl-libs | 1:1.1.1c-2.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:openssl-libs-debuginfo | 1:1.1.1c-2.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:openssl-perl | 1:1.1.1c-2.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| suse:openssl-1_1 | 1.1.0i-4.21.1 · SUSE:Linux Enterprise Module for Basesystem 15 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Joran Dirk GreefRonomon
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-327 · Use of a Broken or Risky Cryptographic AlgorithmCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Encryption Brute ForcingCAPEC-20likelihood: Low · Low
- Creating a Rogue Certification Authority CertificateCAPEC-459likelihood: Medium · Very High
- Signature SpoofCAPEC-473
- Signature Spoofing by Improper ValidationCAPEC-475likelihood: Low · High
- Cryptanalysis of Cellular EncryptionCAPEC-608High
- Rooting SIM CardsCAPEC-614High
- CryptanalysisCAPEC-97likelihood: Low · Very High
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (12 more)Show less
- access.redhat.com/errata/RHSA-2019:3700
- git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=ee22257b1418438ebaf54df98af4e24f494d1809
- git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=f426625b6ae9a7831010750490a5f0ad689c5ba3
- kc.mcafee.com/corporate/index?page=content&id=SB10365
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Y3IVFGSERAZLNJCK35TEM2R4726XIH3Z/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZBEV5QGDRFUZDMNECFXUSN5FMYOZDE4V/
- seclists.org/bugtraq/2019/Jul/3
- www.debian.org/security/2019/dsa-4475
- www.openssl.org/news/secadv/20190306.txt
- www.oracle.com/security-alerts/cpuapr2020.html
- www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html
- www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.