TLS process crash via X.509 name-constraint overflow
Published Nov 1, 2022 · Updated Apr 14, 2026
Stack buffer overflow in X.509 name-constraint checking in OpenSSL 3.0.0 through 3.0.6 allows remote attackers to crash TLS processes. The punycode decoder writes an arbitrary number of period bytes from a crafted email-address constraint beyond a fixed stack buffer. Reachability requires a signed malicious certificate or continued verification after path failure; TLS servers must request client certificates, while clients must connect to a malicious server.
Summary
What happened
Stack buffer overflow in X.509 name-constraint checking in OpenSSL 3.0.0 through 3.0.6 allows remote attackers to crash TLS processes. The punycode decoder writes an arbitrary number of period bytes from a crafted email-address constraint beyond a fixed stack buffer. Reachability requires a signed malicious certificate or continued verification after path failure; TLS servers must request client certificates, while clients must connect to a malicious server.
The record
- CVE
- CVE-2022-3786
- Published
- Nov 1, 2022
- Updated
- Apr 14, 2026
- Vendor
- Siemens
- Product
- SIMATIC RTLS Locating Manager
- Classifications
- CWE-120, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 1, 2022CVE publishedPublication date reported by the CVE source.
- Apr 14, 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=V2.13.0.0 <V2.13.0.3
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.
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