LiveActive security incident?Get immediate response
CVE Record

CVE-2021-41141: Missing release of locks in PJSIP

PJSIP is a free and open source multimedia communication library written in the C language implementing standard based protocols such as SIP, SDP, RTP, STUN, TURN, and ICE. In various parts of PJSIP, when error/failure occurs, it is found that the function returns without releasing the currently held locks. This could result in a system deadlock, which cause a denial of service for the users. No release has yet been made which contains the linked fix commit. All versions up to an including 2.11.1 are affected. Users may need to manually apply the patch.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw can make software using PJSIP freeze under certain error conditions because internal locks are not released. The business impact is service availability: VoIP, SIP, or multimedia communication services could become unavailable until recovered. Sources do not show active exploitation.

Executive priority

Treat as a moderate availability risk. It is not presented as exploited or confidentiality-impacting, but communication platforms can be business-critical. Prioritize exposed or high-availability voice and SIP services, then embedded or internal uses.

Technical view

PJSIP/pjproject versions up to and including 2.11.1 can return from failure paths while holding locks, causing deadlock and denial of service. The CVSS 3.1 score is 5.9, with network attack vector, high complexity, no privileges, no user interaction, and high availability impact.

Likely exposure

Exposure is most likely where pjproject/PJSIP is embedded in SIP, VoIP, or multimedia communication applications, especially custom builds or packages at version 2.11.1 or older.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. The advisory describes denial of service through deadlock, not data theft or code execution. Attack complexity is rated high.

Researcher notes

Focus validation on version provenance and patch presence. The sources identify CWE-667 and a deadlock from unreleased locks on error paths. Evidence is incomplete for exploitability details, affected downstream products, and universal fixed release status beyond cited vendor and distro advisories.

Mitigation direction

  • Inventory products and services that include PJSIP or pjproject.
  • Upgrade via available distribution security updates where applicable.
  • For affected upstream builds, apply the linked pjproject fix commit as directed.
  • Track PJSIP vendor guidance for fixed releases and package availability.
  • Prioritize internet-facing SIP or VoIP services first.

Validation and detection

  • Confirm deployed pjproject/PJSIP versions are not 2.11.1 or older.
  • For source builds, verify the linked lock-release fix is present.
  • Check Debian or Gentoo package advisories when using those distributions.
  • Review service monitoring for unexplained SIP or media-service hangs.
  • Confirm recovery procedures exist for communication service deadlocks.
Prepared
Confidence
high
Sources
6

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-667: 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-41141 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
5Source 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-41141Attack 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-667 · source CWE mapping

Improper Locking

Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.