CVE-2022-27928
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 27.x 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 that allows remote unauthenticated attackers to send specially crafted SIP messages causing the software to abort, resulting in denial of service.
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>= 27.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.
-
Identify Pexip Infinity installationLocate the Pexip Infinity management node and access its admin interface or check system inventory for Pexip Infinity presenceAffected if Pexip Infinity software is installed on the system
-
Check installed Pexip Infinity versionAccess the Pexip Infinity admin dashboard or use the CLI command 'show version' to retrieve the running software versionAffected if The version number falls within 27.0 through 27.2.x (anything less than 27.3)
-
Verify SIP handling is enabledCheck the Pexip Infinity configuration for SIP-related settings, typically found under Call Routing or SIP settings in the admin interfaceAffected if SIP functionality is enabled and the system is configured to accept SIP traffic
The environment is affected if Pexip Infinity version is 27.0 or higher but lower than 27.3 AND SIP is enabled, allowing external SIP messages to reach the vulnerable component.
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. If immediate upgrade is not possible, consider network segmentation to limit SIP exposure to untrusted networks.
Pexip Infinity 27.3
- Backup the current Pexip Infinity configuration before initiating any upgrade
- Schedule a maintenance window to perform the upgrade
- Download Pexip Infinity version 27.3 or later from the official Pexip download portal
- Follow the standard Pexip Infinity upgrade procedure for your deployment type (single node or distributed)
- After upgrade, verify that all services are running correctly
- Confirm the SIP functionality is working as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27928 — 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-27928 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