Remote server crash via omitted retry PSK
Published Jul 10, 2025 · Updated Sep 1, 2026
NULL pointer dereference in GnuTLS before 3.8.10 allows remote attackers to crash a TLS server through a crafted TLS 1.3 handshake. After a first Client Hello supplies a PSK and triggers a Hello Retry Request, a second Client Hello without that PSK leaves selected-PSK state referring to a cleared binder. The sequence requires no authentication, but constructing it is nontrivial; the demonstrated consequence is a server-process crash.
Summary
What happened
NULL pointer dereference in GnuTLS before 3.8.10 allows remote attackers to crash a TLS server through a crafted TLS 1.3 handshake. After a first Client Hello supplies a PSK and triggers a Hello Retry Request, a second Client Hello without that PSK leaves selected-PSK state referring to a cleared binder. The sequence requires no authentication, but constructing it is nontrivial; the demonstrated consequence is a server-process crash.
The record
- CVE
- CVE-2025-6395
- Published
- Jul 10, 2025
- Updated
- Sep 1, 2026
- Vendor
- Siemens
- Product
- SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
- Classifications
- CWE-476, 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?
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