CVE-2024-30170: PrivX before 34.0 allows data exfiltration and denial of service via the REST API

This week

CRITICAL 9.1REMOTEUPGRADE

CVE-2024-30170 is a critical-severity flaw (CVSS 9.1) affecting privx. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

PrivX before 34.0 allows data exfiltration and denial of service via the REST API. This is fixed in minor versions 33.1, 32.3, 31.3, and later, and in major version 34.0 and later,

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.1 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 51%)
CISA exploited list	No
Weakness	CWE-400
Published	2024-08-06
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: ssh

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-08-06 14:16 UTCPublished CVE record published
2026-06-17 07:26 UTCUpdated Record last modified

ssh privx UPGRADE

Affected: >= 22.0 and < 31.3 · >= 32.0 and < 32.3 · 33.0

Fixed in: 31.3, 32.3

Safe to downgrade to: a release before 22.0

1. Check installed version

apt-cache policy privx || rpm -q privx || privx --version

2. UPGRADE to 31.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade privx

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade privx

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 22.0 (Debian / Ubuntu)

apt-cache madison privx sudo apt install privx=<VERSION_BEFORE_22.0> sudo apt-mark hold privx

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list privx sudo dnf downgrade privx-<VERSION_BEFORE_22.0> sudo dnf versionlock add privx

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-30170?

privx: upgrade to 31.3, 32.3. Exact commands for each OS are on this page.

Is CVE-2024-30170 being exploited?

CVE-2024-30170 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-30170 affect?

CVE-2024-30170 affects privx. Severity is critical (CVSS 9.1). PrivX before 34.0 allows data exfiltration and denial of service via the REST API. This is fixed in minor versions 33.1, 32.3, 31.3, and later, and in major version 34.0 and later,

How urgent is CVE-2024-30170?

Priority 54/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs