dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-9875

HIGH · 7.1 CVSS v3.1 Published 2024-11-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
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
Okta Privileged Access server agent (SFTD) versions 1.82.0 to 1.84.0 are affected by a privilege escalation vulnerability when the sudo command bundles feature is enabled. To remediate this vulnerability, upgrade the Okta Privileged Access server agent (SFTD) to version 1.87.1 or greater.

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

Okta Privileged Access server agent (SFTD) versions 1.82.0 to 1.84.0 contain a privilege escalation vulnerability that is triggered when the sudo command bundles feature is enabled, allowing authenticated users to elevate their privileges beyond what they should have access to.

MitigationUpgrade the Okta Privileged Access server agent (SFTD) to version 1.87.1 or greater to remediate this privilege escalation vulnerability.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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 SFTD agent is installed
    Check for the presence of the Okta Privileged Access server agent (SFTD) by looking for the SFTD service or process on the system. On Linux, you can run 'systemctl list-units | grep sftd' or 'ps aux | grep sftd' to see if the service is running.
    Affected if The SFTD service or process is not found on the system, meaning the Okta Privileged Access agent is not installed and this CVE does not apply.
  2. Determine installed SFTD version
    Run the command to check the SFTD version. On Linux, this is typically done with 'sftd --version' or by inspecting the installed package version with 'dpkg -l | grep sftd' or 'rpm -qa | grep sftd' depending on the package manager.
    Affected if The installed version falls within the range 1.82.0 to 1.84.0 (inclusive).
  3. Check if sudo command bundles feature is enabled
    Examine the SFTD configuration file to determine whether the sudo command bundles feature is enabled. Look for configuration files in /etc/sftd/ or similar directories, and search for settings related to 'sudo', 'command bundles', or 'privilege elevation'. The exact configuration path varies by deployment.
    Affected if The sudo command bundles feature is enabled in the SFTD configuration, which is a required condition for this privilege escalation vulnerability to be exploitable.
  4. Verify version against affected range
    Compare your installed SFTD version number against the affected range of 1.82.0 to 1.84.0. If the version is 1.82.0, 1.82.1, 1.83.0, 1.83.1, 1.84.0, or any version in between, the system falls within the vulnerable range.
    Affected if The installed version is 1.82.0, 1.83.0, 1.84.0, or any version between 1.82.0 and 1.84.0 inclusive.

You are affected if the Okta Privileged Access server agent (SFTD) is installed with a version between 1.82.0 and 1.84.0 and the sudo command bundles feature is enabled in the configuration.

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 the Okta Privileged Access server agent (SFTD) to version 1.87.1 or greater to remediate this privilege escalation vulnerability.

Recommended fix Moderate confidence

SFTD version 1.87.1 or greater

  1. Backup the current SFTD configuration and any custom settings
  2. Stop the Okta Privileged Access server agent (SFTD) service
  3. Download the SFTD agent version 1.87.1 or greater from the official Okta download repository (help.okta.com)
  4. Install the upgraded SFTD agent package using your system's package manager or the vendor-provided installer
  5. Start the SFTD service and verify it is running
  6. Confirm the installed version is 1.87.1 or greater by checking the agent version
  7. If sudo command bundles feature was disabled as a mitigation, it can be re-enabled after confirming the upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.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-9875 — 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-9875 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