LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32686: Denial of Service in PJSIP

PJSIP is a free and open source multimedia communication library written in C language implementing standard based protocols such as SIP, SDP, RTP, STUN, TURN, and ICE. In PJSIP before version 2.11.1, there are a couple of issues found in the SSL socket. First, a race condition between callback and destroy, due to the accepted socket having no group lock. Second, the SSL socket parent/listener may get destroyed during handshake. Both issues were reported to happen intermittently in heavy load TLS connections. They cause a crash, resulting in a denial of service. These are fixed in version 2.11.1.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-32686 affects PJSIP/pjproject before 2.11.1. Under heavy TLS connection load, SSL socket race and lifetime issues can crash the process. Business impact is service disruption for systems using PJSIP for SIP or media communications. Sources describe denial of service only, not data theft or remote code execution.

Executive priority

Schedule remediation in the normal vulnerability cycle, accelerated for externally reachable or critical voice/media services. The issue is not shown as actively exploited, but a crash in communication infrastructure can still create operational impact and customer-visible downtime.

Technical view

The flaw is a CWE-362 race condition in PJSIP SSL socket handling. Sources cite a callback-versus-destroy race because accepted sockets lacked a group lock, plus listener destruction during handshake. CVSS 3.1 is 5.9 with network reachability, high attack complexity, no privileges, no user interaction, and high availability impact.

Likely exposure

Exposure is most likely in applications, appliances, servers, containers, or Linux packages that include pjproject/PJSIP before 2.11.1 and accept TLS connections. Distribution builds may be fixed through backported security packages, so version strings alone may require vendor advisory confirmation.

Exploitation context

The provided sources say crashes occurred intermittently under heavy TLS connection load. There is no KEV listing and no cited evidence of active exploitation. Treat this as an availability risk for internet-facing or business-critical communication services, with higher concern where restart loops or failover gaps affect operations.

Researcher notes

Focus validation on TLS-enabled PJSIP paths and packaged backports. The advisory indicates intermittent behavior under heavy load, so absence of crashes is not proof of safety. The public fix references group locking and listener lifetime handling; avoid deriving exploit procedures from the patch.

Mitigation direction

  • Upgrade pjproject/PJSIP to 2.11.1 or later.
  • Apply Debian, Gentoo, or other distribution security updates where packaged.
  • Check vendor guidance for products embedding pjproject/PJSIP.
  • Prioritize public-facing or high-availability TLS communication services.
  • Use service supervision and redundancy to reduce outage impact.

Validation and detection

  • Inventory systems and SBOMs for pjproject or PJSIP usage.
  • Verify installed or embedded versions are 2.11.1 or vendor-patched.
  • Confirm exposed SIP/media services using TLS are covered.
  • Review crash logs for SSL socket failures during connection load.
  • Document vendor backport evidence for packaged deployments.
Prepared
Confidence
high
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-362: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-32686 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H2.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2021-32686Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
pjsippjproject< 2.11.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-362 · source CWE mapping

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.