dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-47857

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-31
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
SSH Communication Security PrivX versions between 18.0-36.0 implement insufficient validation on public key signatures when using native SSH connections via a proxy port. This allows an existing PrivX "account A" to impersonate another existing PrivX "account B" and gain access to SSH target hosts to which the "account B" has access.

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 · high confidence

PrivX versions 18.0-36.0 contain insufficient validation of public key signatures when processing native SSH connections through the proxy port. This allows an authenticated user (account A) to craft maliciously modified SSH key signatures that impersonate another user (account B), bypassing PrivX's internal authorization checks and gaining unauthorized access to SSH target hosts that account B has permissions to access.

MitigationUpgrade PrivX to version 36.1 or later which contains proper public key signature validation. In the interim, restrict proxy port access to only trusted networks and monitor for unusual access patterns indicating user impersonation.

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
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. Confirm PrivX version
    Retrieve the installed PrivX version number using the product's version command, admin UI, or configuration file, then compare against the affected range 18.0 through 36.0
    Affected if The installed version falls within 18.0-36.0 inclusive
  2. Verify proxy port is in use
    Identify whether the PrivX proxy port (used for native SSH connections) is enabled and actively used in the environment through configuration review or network listening status
    Affected if The proxy port is enabled and receiving SSH connection traffic
  3. Assess proxy port network exposure
    Review network access controls, firewall rules, or ACLs governing access to the PrivX proxy port to determine if it is accessible from untrusted networks
    Affected if The proxy port is accessible from networks outside the trusted perimeter

Environment is affected if PrivX version is 18.0-36.0 and the SSH proxy port feature is enabled and accessible, allowing the signature validation bypass to be exploited.

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 PrivX to version 36.1 or later which contains proper public key signature validation. In the interim, restrict proxy port access to only trusted networks and monitor for unusual access patterns indicating user impersonation.

Recommended fix Moderate confidence

PrivX version 36.0 or later (contact SSH Communication Security for exact patched release number)

  1. 1. Identify your current PrivX version by checking the PrivX administration interface or running: privx-api-ctl status or checking /opt/privx/etc/version
  2. 2. Confirm the affected version is between 18.0-36.0 by comparing your current version against this range
  3. 3. Contact SSH Communication Security (via info.ssh.com or ssh.com) to obtain the specific patched version number for version 36.0+
  4. 4. Before upgrading, backup your PrivX database and configuration files: cp -r /opt/privx /opt/privx-backup-$(date +%Y%m%d)
  5. 5. Review the official PrivX upgrade documentation for version 36.0 or later
  6. 6. Perform the upgrade following vendor-provided upgrade procedures, typically via: sudo privx-upgrade or your package manager
  7. 7. After upgrade, verify the new version is installed and the PrivX service is running
  8. 8. Test that native SSH connections via proxy port properly validate public key signatures by attempting to verify that account A can no longer impersonate account B
Caveat Review release notes for version 36.0+ for any configuration or feature changes; may require reconfiguration of proxy port settings

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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