CVE-2022-27931
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPexip Infinity before 27.3 allows remote attackers to trigger a software abort via the Session Initiation Protocol.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencePexip Infinity versions before 27.3 contain a vulnerability in their Session Initiation Protocol (SIP) handling component. Remote attackers can send specially crafted SIP requests to the affected system that trigger a software abort, causing a denial-of-service condition.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 24.0, < 27.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine Pexip Infinity versionLog into the Pexip Infinity admin interface or use the command line interface to retrieve the installed software version. Navigate to the system status or about section in the administration dashboard.Affected if The installed version is 24.0 or higher but lower than 27.3
-
Confirm SIP handling is enabledIn the Pexip Infinity admin interface, verify whether the SIP component is configured and enabled. Check the SIP settings under the relevant conference node or SIP profile configuration.Affected if SIP handling is enabled and the version falls within the vulnerable range
-
Assess network exposure of SIP serviceReview network configuration to determine if the SIP service is accessible from untrusted or external networks. Check firewall rules and node placement to see if SIP ports (typically UDP/TCP 5060) are exposed to the internet or untrusted internal segments.Affected if The SIP service is reachable from untrusted networks and the version is within the affected range
You are affected if Pexip Infinity version is 24.0 or higher but below 27.3 AND the SIP handling component is enabled and exposed to untrusted networks, as the vulnerability can be triggered by specially crafted SIP requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped27.3
Upgrade Pexip Infinity to version 27.3 or later to remediate this vulnerability. Consider implementing network segmentation or SIP-aware firewall rules to limit exposure to untrusted networks until the upgrade can be performed.
27.3 or later
- Upgrade Pexip Infinity to version 27.3 or later
- After upgrade, verify the system is running the patched version
- Test Session Initiation Protocol (SIP) functionality to confirm normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27931 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-27931 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data