CVE-2021-42555
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 26.2 allows temporary remote Denial of Service (abort) because of missing call-setup input validation.
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 before version 26.2 contains missing input validation during call-setup processing, allowing remote attackers to trigger an abort condition that causes a denial of service.
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>= 25.0, < 26.2CVSS 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 if Pexip Infinity is installedCheck the system for Pexip Infinity components or consult your Pexip deployment documentation to confirm the product is present in your environmentAffected if Pexip Infinity is not installed on the system
-
Determine the installed Pexip Infinity versionAccess the Pexip Infinity admin interface and navigate to the version information page, or run the command 'pexctl show version' on the management node if CLI access is availableAffected if The version cannot be determined or is not displayed
-
Compare your version to the affected rangeReview the installed version number and verify whether it falls within the range >= 25.0 and < 26.2Affected if The installed version is 25.0, 25.1, 25.2, 25.3, 26.0, or 26.1 (any version from 25.0 up to but not including 26.2)
-
Verify call-processing is enabledCheck the Pexip Infinity admin interface under Conference > Settings or the call routing configuration to confirm the system is configured to accept and process callsAffected if Call-processing functionality is enabled and the system can receive incoming call requests
You are affected if Pexip Infinity is installed with any version from 25.0 through 26.1 (versions below 26.2) and the system has call-processing enabled to accept incoming calls.
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 · scoped26.2
Upgrade Pexip Infinity to version 26.2 or later to obtain the missing input validation controls.
Upgrade to Infinity version 26.2 or later
- Verify current Pexip Infinity version by accessing the admin interface or checking system information
- Plan maintenance window as upgrade may require service restart
- Obtain Pexip Infinity 26.2 or later upgrade package from official Pexip distribution channels
- Follow standard Pexip Infinity upgrade procedure - typically via admin web interface or management node
- Verify successful upgrade and confirm services are operational
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-42555 — 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-42555 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