dbcve.org
Pexip InfinityApplication · Pexip

CVE-2020-11805

CRITICAL · 9.8 CVSS v3.1 Published 2020-09-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Reverse Proxy and TURN Server before 6.1.0 has Incorrect UDP Access Control via TURN.

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

The Pexip Reverse Proxy and TURN Server before version 6.1.0 contains an incorrect UDP access control vulnerability in its TURN (Traversal Using Relays around NAT) server component. This allows unauthorized users to potentially access and relay traffic through the TURN server via UDP, which could be exploited for traffic relay, firewall bypass, or amplification attacks.

MitigationUpgrade Pexip Reverse Proxy and TURN Server to version 6.1.0 or later to remediate the incorrect UDP access control. If immediate upgrading is not possible, implement strict firewall rules to limit TURN server access to authorized endpoints only.

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.1
Reverse Proxy And Turn ServerApplication
Affected:= 6.0.7= 6.0.10

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 the installed Pexip Reverse Proxy and TURN Server version
    Check the version of the Pexip Reverse Proxy and TURN Server software currently deployed in your environment. This is typically visible in the admin interface, system information page, or by querying the installed software package.
    Affected if The installed version is 6.0.7 or 6.0.10, or any version prior to 6.1.0.
  2. Identify the Pexip Infinity version if applicable
    If Pexip Infinity is deployed, check its version number from the admin console or system information.
    Affected if The installed Pexip Infinity version is 23 or 23.1.
  3. Verify the TURN server component is enabled
    Confirm whether the TURN server functionality is enabled in the Pexip deployment. This is typically configurable in the server settings or admin interface.
    Affected if The TURN server component is enabled and accepting UDP connections.
  4. Inspect UDP access control configuration for TURN
    Review the TURN server access control settings to determine if UDP traffic is restricted to authorized endpoints or open to any source.
    Affected if UDP access control is not properly configured or allows unauthenticated access.
  5. Check for unauthorized TURN relay connections
    Monitor TURN server logs or connection records for any unexpected or unauthorized relay connections from external sources.

You are affected if your Pexip Reverse Proxy and TURN Server version is 6.0.7, 6.0.10, or any version before 6.1.0 (or Pexip Infinity versions 23 or 23.1) AND the TURN server is enabled with UDP access open to unauthorized users.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Pexip Reverse Proxy and TURN Server to version 6.1.0 or later to remediate the incorrect UDP access control. If immediate upgrading is not possible, implement strict firewall rules to limit TURN server access to authorized endpoints only.

Recommended fix Moderate confidence

Pexip Infinity 6.1.0 or later

  1. 1. Identify current version of Pexip Reverse Proxy and TURN Server by checking the administration interface or running system diagnostics
  2. 2. Obtain Pexip Infinity version 6.1.0 or later from the official Pexip download portal at docs.pexip.com
  3. 3. Review the Pexip upgrade documentation for proper upgrade procedures
  4. 4. Perform a backup of the current configuration before upgrading
  5. 5. Apply the upgrade following the documented steps in the Pexip administration guide
  6. 6. Verify the upgraded version is 6.1.0 or later in the administration interface
  7. 7. Test TURN server functionality to confirm the UDP access control vulnerability is remediated

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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