CVE-2022-27930
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 single-sign-on if a random Universally Unique Identifier is guessed.
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 27.x before 27.3 contains a denial-of-service vulnerability in the Single Sign-On (SSO) authentication mechanism. An unauthenticated remote attacker can trigger a software abort (crash) by successfully guessing a random UUID used in the SSO process, causing the service to become unavailable.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 versionLocate the installed version of Pexip Infinity in the administration interface or system inventoryAffected if The installed version is 27.0, 27.1, or 27.2 (any version >= 27.0 but < 27.3)
-
Confirm SSO is enabledCheck whether the Single Sign-On (SSO) authentication feature is configured and active in the Pexip Infinity deploymentAffected if SSO authentication is enabled and accessible to unauthenticated users
-
Verify SSO endpoint exposureInspect network configuration to determine if the SSO endpoint is exposed to untrusted networks or the public internetAffected if The SSO endpoint is reachable from untrusted or external networks without additional access controls
A user is affected if their Pexip Infinity version is 27.0 through 27.2 and SSO is enabled and accessible to unauthenticated attackers.
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 to Pexip Infinity version 27.3 or later. If immediate upgrade is not feasible, consider implementing rate limiting or IP-based access controls on the SSO endpoint to reduce the likelihood of successful UUID guessing attacks.
27.3 or later
- Back up the current Pexip Infinity configuration and database
- Download Pexip Infinity version 27.3 or later from the official Pexip portal
- Follow the standard Pexip upgrade documentation to install the update
- After upgrade, verify the SSO functionality is working correctly and no software aborts occur
- Confirm the version number shows 27.3 or higher in the admin interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27930 — 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-27930 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