TLS server crash via SSL socket races
Published Jul 23, 2021 · Updated Nov 4, 2025
Race conditions in the SSL socket server in PJSIP PJPROJECT before 2.11.1 allow remote attackers to crash TLS servers. The accepted active socket is created without its group lock, while the parent listener can be destroyed during a handshake and verify_cb relies on an assertion rather than runtime validation. Triggering either lifetime race requires heavy concurrent incoming TLS connections; client applications are generally unaffected unless they accept such connections.
Summary
What happened
Race conditions in the SSL socket server in PJSIP PJPROJECT before 2.11.1 allow remote attackers to crash TLS servers. The accepted active socket is created without its group lock, while the parent listener can be destroyed during a handshake and verify_cb relies on an assertion rather than runtime validation. Triggering either lifetime race requires heavy concurrent incoming TLS connections; client applications are generally unaffected unless they accept such connections.
The record
- CVE
- CVE-2021-32686
- Published
- Jul 23, 2021
- Updated
- Nov 4, 2025
- Vendor
- PJSIP
- Product
- PJPROJECT
- Classifications
- CWE-362, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 23, 2021CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record 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=< 2.11.1
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