Application crash via otherName SAN double free
Published Jul 10, 2025 · Updated Sep 1, 2026
Double free in GnuTLS before 3.8.10 allows remote attackers to crash applications via malformed otherName SAN export input. The export error path calls asn1_delete_structure() on an ASN.1 node it does not own, and later cleanup frees the node again. Reachability requires an application to pass a malformed type-id OID through the public export APIs; allocator behavior determines whether the result is a crash or memory corruption.
Summary
What happened
Double free in GnuTLS before 3.8.10 allows remote attackers to crash applications via malformed otherName SAN export input. The export error path calls asn1_delete_structure() on an ASN.1 node it does not own, and later cleanup frees the node again. Reachability requires an application to pass a malformed type-id OID through the public export APIs; allocator behavior determines whether the result is a crash or memory corruption.
The record
- CVE
- CVE-2025-32988
- Published
- Jul 10, 2025
- Updated
- Sep 1, 2026
- Vendor
- Siemens
- Product
- SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
- Classifications
- CWE-415, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 10, 2025CVE publishedPublication date reported by the CVE source.
- Sep 1, 2026Record 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=V3.1.5 <*
What conditions does exploitation require?
What is affected?
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.
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