dbcve.org
Pexip InfinityApplication · Pexip

CVE-2018-10432

HIGH · 7.5 CVSS v3.1 Published 2020-09-25
Fix available
A fix is available. Upgrade to 18 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 18 allows Remote Denial of Service (TLS handshakes in RTMP).

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 prior to 18 contain a vulnerability in the RTMP (Real-Time Messaging Protocol) handling that allows remote attackers to cause a Denial of Service via crafted TLS handshakes. The vulnerability is exploitable remotely without authentication.

MitigationUpgrade Pexip Infinity to version 18 or later to remediate this vulnerability. If immediate upgrade is not feasible, consider network segmentation to limit exposure of the RTMP service to untrusted 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:>= 9, < 18

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
    Log into the Pexip Infinity admin console or use the command line interface to determine the currently installed version number
    Affected if The installed version is less than 18 (versions 9 through 17.x are affected)
  2. Locate RTMP service configuration
    In the Pexip Infinity admin interface, navigate to the conferencing settings or service configuration section to find RTMP-related settings
    Affected if RTMP functionality is enabled on the system
  3. Verify RTMP over TLS is configured
    Check the RTMP service settings to confirm whether TLS encryption is enabled for RTMP connections
    Affected if TLS is enabled for RTMP, as the vulnerability is exploited via crafted TLS handshakes
  4. Confirm RTMP network exposure
    Review network configuration to determine if the RTMP service port (typically 1935 for RTMP, 443 for RTMPS) is exposed to external networks or untrusted interfaces
    Affected if The RTMP service is accessible from untrusted or external network segments

The environment is affected if Pexip Infinity version is below 18 and the RTMP service with TLS is exposed to untrusted networks.

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 18 or later
Fixed in 18
Interim mitigation

Upgrade Pexip Infinity to version 18 or later to remediate this vulnerability. If immediate upgrade is not feasible, consider network segmentation to limit exposure of the RTMP service to untrusted networks.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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