Authentication bypass via uninitialized session-ticket key
Published Jun 4, 2020 · Updated Aug 4, 2024
Cryptographic flaw in GnuTLS 3.6.4 through 3.6.13 allows man-in-the-middle attackers to bypass TLS 1.3 authentication via session resumption. In lib/stek.c, initial session-ticket setup records the TOTP timestamp without initializing the application-supplied key, so tickets use wrong key data until rotation. An active network interception position is required; successful attacks bypass TLS 1.3 authentication or recover earlier TLS 1.2 conversations.
Summary
What happened
Cryptographic flaw in GnuTLS 3.6.4 through 3.6.13 allows man-in-the-middle attackers to bypass TLS 1.3 authentication via session resumption. In lib/stek.c, initial session-ticket setup records the TOTP timestamp without initializing the application-supplied key, so tickets use wrong key data until rotation. An active network interception position is required; successful attacks bypass TLS 1.3 authentication or recover earlier TLS 1.2 conversations.
The record
- CVE
- CVE-2020-13777
- Published
- Jun 4, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-327, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 4, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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