CVE-2021-29655
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 Connect before 1.8.0 omits certain provisioning authenticity checks. Thus, untrusted code may execute.
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 Connect before version 1.8.0 contains a vulnerability where the provisioning process lacks proper authenticity checks, allowing attackers to inject and execute untrusted code remotely. This critical RCE vulnerability stems from missing validation during the provisioning workflow.
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< 1.8.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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Check installed Pexip Infinity Connect versionOpen the Pexip Infinity Connect client and navigate to Help > About, or check the application version in the installed programs list (Windows: Programs and Features, macOS: Applications folder)Affected if The version displayed is earlier than 1.8.0
-
Check provisioning configuration via admin portalLog into the Pexip Infinity admin web interface and navigate to Platform > Provisioning or Settings > Provisioning to see if provisioning is configured and enabledAffected if Provisioning is enabled and the client version is below 1.8.0
-
Verify provisioning server authenticityReview the provisioning server URL configured in the client or admin portal. Check if the server is a trusted internal Pexip deployment rather than an untrusted or externally accessible provisioning endpointAffected if Provisioning points to an untrusted or externally accessible server and the client version is below 1.8.0
-
Check deployment inventory for all Pexip clientsUse endpoint management tools or software inventory to enumerate all installed Pexip Infinity Connect instances across the environment and record their versionsAffected if Any Pexip Infinity Connect instance found with version below 1.8.0 is affected if provisioning is in use
The environment is affected if any Pexip Infinity Connect client version is below 1.8.0 and the provisioning feature is enabled or configured.
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 · scoped1.8.0
Upgrade Pexip Infinity Connect to version 1.8.0 or later to remediate the missing authenticity checks in the provisioning process.
1.8.0
- Upgrade Pexip Infinity Connect to version 1.8.0 or later to remediate the authenticity check vulnerability
- Verify the upgrade was successful and the provisioning authenticity checks are now enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29655 — 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-2021-29655 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