CVE-2022-27933
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 cause a software abort, resulting in denial of service. The specific vulnerability type and exact cause are not detailed in the available description.
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
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 if Pexip Infinity is deployedLocate Pexip Infinity installation in your environment. This is typically a video conferencing platform deployed as virtual machines or appliances. Check your infrastructure inventory or documentation for Pexip deployments.Affected if Pexip Infinity is not present in your environment - you are not affected
-
Determine the installed Pexip Infinity versionAccess the Pexip Infinity admin interface or use the command-line management tools to retrieve the current software version. Compare your version number against the affected range: versions 24.0 through 27.2 are vulnerable.Affected if Your version is 24.0 or higher but lower than 27.3 - you are in the affected range
-
Verify if One Touch Join feature is enabledCheck the Pexip Infinity admin interface configuration settings for the One Touch Join feature. This feature allows users to join conferences with a single touch. Inspect the conference settings, deployment settings, or participant configuration where this feature would be toggled.Affected if One Touch Join is enabled and your version falls within the affected range - you are vulnerable to the DoS condition
You are affected if Pexip Infinity version 24.0 or higher but lower than 27.3 is deployed with the One Touch Join feature enabled, as this combination allows remote attackers to trigger a software abort causing denial of service.
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
Update Pexip Infinity to version 27.3 or later to remediate this vulnerability.
Pexip Infinity 27.3 or later
- Obtain Pexip Infinity version 27.3 or later from the official vendor (docs.pexip.com)
- Follow standard Pexip Infinity upgrade procedures to apply the update
- Verify the upgrade was successful and the One Touch Join functionality is working correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27933 — 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-27933 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