dbcve.org
Pexip InfinityApplication · Pexip

CVE-2020-12824

HIGH · 7.5 CVSS v3.1 Published 2020-09-25
Fix available
A fix is available. Upgrade to 23.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Pexip Infinity 23.x before 23.3 has improper input validation, leading to a temporary software abort via RTP.

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 confidence

Pexip Infinity versions 23.x before 23.3 contain improper input validation in RTP (Real-time Transport Protocol) handling. An attacker sending specially crafted RTP packets to a vulnerable instance can trigger a temporary software abort, causing a denial of service condition.

MitigationUpgrade Pexip Infinity to version 23.3 or later to remediate this vulnerability. If immediate upgrading is not possible, consider implementing network-level controls to restrict RTP traffic to trusted sources.

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
Pexip InfinityApplication
Affected:>= 23, < 23.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Pexip Infinity version
    Access the Pexip Infinity admin interface and navigate to Platform > Diagnostics > Version, or run 'pexconf --show-version' via CLI if available
    Affected if The displayed version is 23.x where x is any version before 23.3 (e.g., 23.0, 23.1, 23.2)
  2. Confirm RTP processing is enabled
    In the Pexip admin interface, verify that Conferencing Nodes are configured to accept RTP/RTCP media streams. Check under Platform > Conferencing Nodes or similar media configuration sections
    Affected if RTP media handling is enabled, which is the default configuration for typical Pexip deployments handling video/audio calls
  3. Check network exposure to untrusted RTP sources
    Review firewall rules and access controls to determine whether the Conferencing Nodes' RTP ports (typically UDP 50000-60000 range) are exposed to untrusted network segments or the public internet
    Affected if RTP ports are accessible from untrusted networks or the internet without filtering

A Pexip Infinity installation is affected if it runs version 23.0, 23.1, or 23.2 and processes RTP traffic from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 23.3 or later
Fixed in 23.3
Interim mitigation

Upgrade Pexip Infinity to version 23.3 or later to remediate this vulnerability. If immediate upgrading is not possible, consider implementing network-level controls to restrict RTP traffic to trusted sources.

Fix this in Pexip Infinity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-12824 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-12824 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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