CVE-2022-27932
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 One Touch Join.
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 the One Touch Join feature that allows remote attackers to trigger a software abort, causing a denial-of-service condition. The vulnerability is exploitable remotely without authentication.
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.
-
Identify installed Pexip Infinity versionAccess the Pexip Infinity admin interface and navigate to the Dashboard or System > General > About page to view the current software version. Alternatively, use the CLI command 'version' or check the '/opt/pexip/version.txt' file if you have shell access.Affected if The installed version is 24.0 or later but earlier than 27.3
-
Verify One Touch Join feature statusIn the Pexip Infinity admin interface, navigate to Call Routing > One Touch Join or Settings > One Touch Join to confirm whether the feature is enabled. Check the configuration file or registry for 'one_touch_join_enabled' or similar setting if using CLI.Affected if One Touch Join is enabled on the system
-
Confirm network exposure of the management interfaceReview firewall rules and network ACLs to determine if the Pexip Infinity admin interface or API endpoints are accessible from untrusted networks. Check if the management port (typically 443) is exposed to the internet or external VLANs.Affected if The Pexip Infinity management interface is reachable from untrusted networks without authentication barriers
You are affected if your Pexip Infinity version is between 24.0 and 27.3 (inclusive) and the One Touch Join feature is enabled and accessible remotely.
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. Prior to upgrading, assess current deployment version and schedule maintenance window; after upgrade, verify One Touch Join functionality and overall system stability.
Pexip Infinity 27.3
- 1. Back up current Pexip Infinity configuration and data
- 2. Review Pexip Infinity 27.3 release notes for any configuration or feature changes
- 3. Schedule a maintenance window for the upgrade
- 4. Download Pexip Infinity version 27.3 or later from the official Pexip portal
- 5. Upgrade the Pexip Infinity management node first
- 6. Upgrade all conferencing nodes following the standard upgrade procedure
- 7. Verify the One Touch Join functionality is working correctly after upgrade
- 8. Confirm all services are operational
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27932 — 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-27932 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