dbcve.org
Pexip InfinityApplication · Pexip

CVE-2023-31289

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 signalling, 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 before version 31.2 contains an improper input validation vulnerability in its signalling component that allows remote, unauthenticated attackers to send specially crafted input that triggers an application abort, resulting in denial of service.

MitigationUpgrade Pexip Infinity to version 31.2 or later to obtain the patched signalling input validation. If immediate upgrade is not feasible, consider network segmentation and limiting signalling port exposure to trusted networks.

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. Confirm Pexip Infinity is installed
    Check system inventory or running services for Pexip Infinity presence. Look for processes named 'pexip' or services related to the Pexip platform.
    Affected if Pexip Infinity software is found on the system
  2. Identify installed Pexip Infinity version
    Access the Pexip Infinity admin interface or check system documentation for the current deployment version. The version is typically visible in the admin dashboard or via command-line tools provided by Pexip.
    Affected if Version is displayed as lower than 31.2
  3. Verify signalling component is network-accessible
    Determine if the signalling ports (typically TCP 443 or as configured in your deployment) are exposed to untrusted networks. Check firewall rules and network ACLs governing the Pexip Infinity management and signalling interfaces.
    Affected if Signalling component is reachable from untrusted networks or the internet
  4. Confirm version is within vulnerable range
    Compare your identified version against the affected range: versions before 31.2 are vulnerable. Version 31.2 and later include the patched signalling input validation.
    Affected if Installed version is before 31.2 and signalling is network-accessible

You are affected if Pexip Infinity is installed with a version lower than 31.2 and the signalling component is accessible from networks where untrusted attackers could send specially crafted input.

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 patched signalling input validation. If immediate upgrade is not feasible, consider network segmentation and limiting signalling port exposure to trusted networks.

Recommended fix Moderate confidence

31.2

  1. Back up the current Pexip Infinity configuration and data before initiating the upgrade
  2. Download the Pexip Infinity version 31.2 upgrade package from the official Pexip download portal
  3. Apply the upgrade to the Pexip Infinity deployment following the standard upgrade procedure documented in the Pexip admin documentation
  4. After upgrade completion, verify that all services are running correctly and the signalling component is functioning as expected
  5. Review the admin interface to confirm the running version is 31.2
Caveat Review Pexip release notes for version 31.2 to check for any configuration or feature changes that may affect your deployment

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

Fix this in Pexip Infinity Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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