Skip to content
Noroxi
NVD / CVE Program· CNA openssl

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).

HighCVSS 7.4 · v3.0—No exploit Fix available
Published
Mar 6, 2019
Updated
Jun 16, 2026
EPSS
5.7% · 93th percentile

Report tools

JSON

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.

Follow CVE-2019-1543

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
opensslopenssl

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 check

Affected 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.

EcosystemPackageAffected rangeFix
Alpine:v3.10filebefore 5.36-r05.36-r0
Alpine:v3.10opensslfrom 1.1.0 · before 1.1.1b-r11.1.1b-r1
Alpine:v3.15openssl3before 1.1.1b-r11.1.1b-r1
Debian:12opensslbefore 1.1.1c-11.1.1c-1
Debian:9opensslbefore 1.1.0k-1~deb9u11.1.0k-1~deb9u1
openSUSE:Leap 15.0openssl-1_1before 1.1.0i-lp150.3.22.31.1.0i-lp150.3.22.3
openSUSE:Leap 15.0virtualboxbefore 6.0.10-lp151.2.6.16.0.10-lp151.2.6.1
Red Hat:enterprise_linux:8::baseosopensslbefore 1:1.1.1c-2.el81:1.1.1c-2.el8
Red Hat:enterprise_linux:8::baseosopenssl-debuginfobefore 1:1.1.1c-2.el81:1.1.1c-2.el8
Red Hat:enterprise_linux:8::baseosopenssl-debugsourcebefore 1:1.1.1c-2.el81:1.1.1c-2.el8
Red Hat:enterprise_linux:8::baseosopenssl-develbefore 1:1.1.1c-2.el81:1.1.1c-2.el8
Red Hat:enterprise_linux:8::baseosopenssl-libsbefore 1:1.1.1c-2.el81:1.1.1c-2.el8
Red Hat:enterprise_linux:8::baseosopenssl-libs-debuginfobefore 1:1.1.1c-2.el81:1.1.1c-2.el8
Red Hat:enterprise_linux:8::baseosopenssl-perlbefore 1:1.1.1c-2.el81:1.1.1c-2.el8
SUSE:Linux Enterprise Desktop 12 SP4openssl-1_1before 1.1.1-2.9.11.1.1-2.9.1
SUSE:Linux Enterprise Module for Basesystem 15openssl-1_1before 1.1.0i-4.21.11.1.0i-4.21.1

Other 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 remKEV
    90Now
  • CVE-2021-3711SM2 Decryption Buffer Overflow
    65This 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 DSA
    27Monitor
  • ← EarlierCVE-2019-1559Feb 27, 2019 · 0-byte record padding oracle
    28Monitor
  • Later →CVE-2019-1552Jul 30, 2019 · Windows builds with insecure path defaults
    13Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:file5.36-r0 · Alpine:v3.10Package registry (OSV)
alpine:openssl1.1.1b-r1 · Alpine:v3.10Package registry (OSV)
alpine:openssl31.1.1b-r1 · Alpine:v3.15Package registry (OSV)
debian:openssl1.1.1c-1 · Debian:12Package registry (OSV)
opensuse:openssl-1_11.1.0i-lp150.3.22.3 · openSUSE:Leap 15.0Package registry (OSV)
opensuse:virtualbox6.0.10-lp151.2.6.1 · openSUSE:Leap 15.0Package registry (OSV)
red hat:openssl1:1.1.1c-2.el8 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:openssl-debuginfo1:1.1.1c-2.el8 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:openssl-debugsource1:1.1.1c-2.el8 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:openssl-devel1:1.1.1c-2.el8 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:openssl-libs1:1.1.1c-2.el8 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:openssl-libs-debuginfo1:1.1.1c-2.el8 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:openssl-perl1:1.1.1c-2.el8 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
suse:openssl-1_11.1.0i-4.21.1 · SUSE:Linux Enterprise Module for Basesystem 15Package 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.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

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

CVSS vector

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records