dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2024-38392

CRITICAL · 9.1 CVSS v3.1 Published 2025-04-02
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 Infinity Connect before 1.13.0 lacks sufficient authenticity checks during the loading of resources, and thus remote attackers can cause the application to run untrusted code.

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 Connect before version 1.13.0 contains a critical vulnerability where insufficient authenticity checks during the loading of resources allows remote attackers to inject and execute untrusted code. This is a remote code execution vulnerability exploitable without authentication.

MitigationUpgrade Pexip Infinity Connect to version 1.13.0 or later which implements proper authenticity validation for loaded resources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Verify Pexip Infinity Connect version
    Open the Pexip Infinity Connect client and access the About or Help section to view the installed version number. Alternatively, check the application's installer file or system registry entry for the version information.
    Affected if the installed version is before 1.13.0

A user is affected if Pexip Infinity Connect is installed and running a version prior to 1.13.0.

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 Infinity Connect to version 1.13.0 or later which implements proper authenticity validation for loaded resources.

Recommended fix Moderate confidence

Pexip Infinity Connect 1.13.0 or later

  1. 1. Identify all deployed instances of Pexip Infinity Connect in your environment
  2. 2. Check the version number of each instance (typically available in the application UI or admin console)
  3. 3. Navigate to the official Pexip documentation at docs.pexip.com to obtain the version 1.13.0 or later installer
  4. 4. Review upgrade documentation and release notes for any prerequisites or migration requirements
  5. 5. Back up current configuration data according to Pexip backup procedures
  6. 6. Perform the upgrade following the documented upgrade path for your deployment type
  7. 7. Verify the upgrade was successful and the application is functioning correctly
  8. 8. Confirm the version now shows 1.13.0 or later
Caveat Review Pexip release notes for any configuration or feature changes between your current version and 1.13.0

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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