dbcve.org
Pexip InfinityApplication · Pexip

CVE-2023-31455

HIGH · 7.5 CVSS v3.1 Published 2023-12-25
Fix available
A fix is available. Upgrade to 31.2 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 before 31.2 has Improper Input Validation for RTCP, allowing remote attackers to trigger an abort.

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 before 31.2 contain improper input validation in the RTCP (Real-time Transport Control Protocol) handling component. Remote attackers can send specially crafted RTCP packets that trigger an abort condition, resulting in denial of service. The vulnerability lies in how the application processes incoming RTCP data without adequate validation of packet contents or structure.

MitigationUpgrade Pexip Infinity to version 31.2 or later to obtain the vendor patch. If immediate upgrade is not feasible, consider network-level filtering of untrusted RTCP traffic at the perimeter, though this may impact legitimate conferencing functionality.

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:< 31.2

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 installation
    Locate Pexip Infinity components in your environment using system inventory or asset discovery tools. Check for Pexip Infinity admin nodes, conferencing nodes, or management interfaces.
    Affected if Pexip Infinity is not present in your environment - you are not affected.
  2. Determine installed Pexip Infinity version
    Access the Pexip Infinity admin interface or use the command-line interface to retrieve the software version. Typically found under Administration > Software or via 'version' command in CLI.
    Affected if The installed version is any version before 31.2 (e.g., 31.1, 31.0, 30.x, earlier).
  3. Verify RTCP processing is active
    Check if the conferencing nodes are configured to handle media streams. RTCP is part of standard media processing for video conferencing. Inspect node status in admin interface or check if media ports (typically UDP ports in the 50000-60000 range) are in use.
    Affected if RTCP processing is enabled and media handling is active - the vulnerable component is in use.
  4. Review system logs for RTCP-related anomalies
    Examine Pexip Infinity diagnostic logs or system logs for crash reports, abort conditions, or error messages mentioning RTCP, media processing failures, or unexpected service restarts.
    Affected if Logs show recent crashes or aborts related to RTCP packet processing.

You are affected if Pexip Infinity is installed with a version lower than 31.2 and the RTCP handling component is active (which is typically the default for conferencing functionality).

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.

dbcve · scoped
Upgrade available Upgrade to 31.2 or later
Fixed in 31.2
Interim mitigation

Upgrade Pexip Infinity to version 31.2 or later to obtain the vendor patch. If immediate upgrade is not feasible, consider network-level filtering of untrusted RTCP traffic at the perimeter, though this may impact legitimate conferencing functionality.

Recommended fix High confidence

31.2

  1. Schedule a maintenance window for the upgrade procedure
  2. Back up the current Pexip Infinity configuration and database
  3. Download Pexip Infinity version 31.2 from the official Pexip portal (docs.pexip.com)
  4. Follow the official Pexip upgrade documentation to apply the version 31.2 update
  5. Verify the upgrade was successful by checking the admin interface and system status
  6. Test RTCP functionality to confirm the improper input validation issue is resolved
Caveat Standard minor version upgrade - minimal risk, but always test in staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pexip Infinity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31455 — 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-2023-31455 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