CVE-2022-29286
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 before 28.0 allows remote attackers to trigger excessive resource consumption and termination because of registrar resource mishandling.
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 prior to 28.0 contain a vulnerability in the registrar component where resource handling is improper, allowing remote attackers to trigger excessive resource consumption leading to service termination.
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, < 28.0CVSS 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 installation and determine the installed version number. This is typically available in the admin interface under System > Overview, or via CLI command such as 'version' or 'show version' if you have SSH access to the Pexip server.Affected if Pexip Infinity software is found on the system
-
Confirm the exact version numberRecord the full version string of the Pexip Infinity installation. Look for a version in the format like 27.x.x or similar.Affected if A version number cannot be determined or the software is not Pexip Infinity
-
Compare against affected version rangeCheck if the installed version falls within the range >= 27.0 and < 28.0. Parse the major and minor version numbers to determine if the vulnerability applies.Affected if The installed version is 27.0 or any 27.x release but earlier than 28.0
The environment is affected if the installed Pexip Infinity version is 27.0 or higher but lower than 28.0, as this is the only version range specified as vulnerable to the registrar resource handling flaw.
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 · scoped28.0
Upgrade Pexip Infinity to version 28.0 or later to address the registrar resource mishandling vulnerability.
28.0
- 1. Review Pexip Infinity 28.0 release notes for any pre-upgrade requirements
- 2. Ensure you have a backup of the current configuration
- 3. Upgrade Pexip Infinity from version 27.x to version 28.0
- 4. Verify the upgrade completed successfully
- 5. Confirm the registrar resource handling is functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29286 — 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-29286 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