CVE-2020-25868
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 22.x through 24.x before 24.2 has Improper Input Validation for call setup. An unauthenticated remote attacker can trigger a software abort (temporary loss of service).
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 22.x through 24.x before 24.2 contains an improper input validation vulnerability in the call setup functionality. An unauthenticated remote attacker can send specially crafted requests during call setup that trigger a software abort, resulting in temporary 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>= 22.0, < 24.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 the installed Pexip Infinity versionLog into the Pexip Infinity admin interface and navigate to the Dashboard or System > About page to view the software version. Alternatively, access the CLI and run the command to display the version (typically 'version' or 'show version').Affected if The displayed version is 22.x, 23.x, or 24.x prior to 24.2, indicating it falls within the vulnerable range.
-
Confirm call setup functionality is enabledAccess the Pexip Infinity admin interface and review the Conferencing > Call Routing or Call Setup configuration sections. Verify whether the call setup functionality that accepts incoming requests is configured and active.Affected if Call setup functionality is enabled and accepting incoming connection requests, making it reachable for exploitation.
-
Determine if call setup is exposed to untrusted networksReview the network accessibility settings for call setup services. Check firewall rules, NAT configurations, or service exposure settings that control whether call setup ports and endpoints are reachable from external or untrusted networks.Affected if Call setup is exposed to networks that are not trusted (such as the public internet or untrusted VLANs), allowing unauthenticated attackers to reach the vulnerable component.
-
Correlate version and exposure for impact assessmentCombine the findings: if the installed version is >= 22.0 and < 24.2 AND call setup is exposed to untrusted networks, the environment is vulnerable to the denial-of-service condition described in the CVE.Affected if Both conditions are true: the version is within 22.0 to < 24.2 AND call setup is network-accessible to unauthenticated attackers.
A Pexip Infinity deployment is affected if it runs version 22.x, 23.x, or 24.x prior to 24.2 AND has call setup functionality exposed to untrusted or external networks, allowing unauthenticated attackers to trigger the denial-of-service condition.
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.
From vendor data24.2
Upgrade Pexip Infinity to version 24.2 or later to obtain the patch for this improper input validation vulnerability. Alternatively, implement network-level access controls to limit call setup exposure to untrusted networks.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25868 — 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-2020-25868 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