Client memory corruption via stale key-share pointer
Published Mar 12, 2021 · Updated Aug 3, 2024
A use-after-free in GnuTLS before 3.7.1 allows remote attackers to corrupt client memory during a TLS 1.3 handshake. The key_share extension sender saves a length pointer before buffer growth can reallocate its storage, then writes through that stale pointer. Reachability requires a large Client Hello, such as an HRR during resumption after large FFDHE parameters, and exploitation depends on allocator behavior.
Summary
What happened
A use-after-free in GnuTLS before 3.7.1 allows remote attackers to corrupt client memory during a TLS 1.3 handshake. The key_share extension sender saves a length pointer before buffer growth can reallocate its storage, then writes through that stale pointer. Reachability requires a large Client Hello, such as an HRR during resumption after large FFDHE parameters, and exploitation depends on allocator behavior.
The record
- CVE
- CVE-2021-20231
- Published
- Mar 12, 2021
- Updated
- Aug 3, 2024
- Vendor
- GnuTLS Project
- Product
- GnuTLS
- Classifications
- T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=gnutls 3.7.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo