CVE-2022-27929
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 HTTP.
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 vulnerability where remote attackers can send specially crafted HTTP requests to trigger a software abort, resulting in denial of service. The attack can be carried out remotely via HTTP 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>= 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.
-
Determine installed Pexip Infinity versionLog into the Pexip Infinity admin interface and check the version displayed on the dashboard, or run the command 'version' from the CLI if you have shell accessAffected if The displayed version is 27.0, 27.1, 27.2, or any 27.2.x point release (versions >= 27.0 and < 27.3)
-
Confirm version is in affected rangeCompare your installed version against the vulnerable range: versions 27.0 through 27.2.x are affected; versions 27.3 and later are notAffected if Your version falls within 27.0 <= version < 27.3
-
Check if management interface is network-accessibleVerify whether the Pexip Infinity management interface (typically ports 443 or 8443) is exposed to untrusted networks or the public internet, or attempt a curl/GET request to the management URL from an external locationAffected if The management interface is reachable from untrusted networks without VPN or firewall filtering (since the attack requires only HTTP access without authentication)
You are affected if your Pexip Infinity version is 27.0, 27.1, or 27.2.x AND the management interface is accessible over HTTP from untrusted networks.
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 upgrading is not feasible, consider placing the management interface behind a firewall or VPN access control to limit exposure to untrusted networks.
27.3
- Identify all Pexip Infinity installations in the environment running versions 27.0 through 27.2
- Check the version of each installation to confirm it is >= 27.0 and < 27.3
- Upgrade each affected installation to version 27.3 or later to remediate the vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27929 — 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-27929 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