Okta Verify for Windows is vulnerable to privilege escalation through DLL hijacking.

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• okta verifybefore 5.0.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Okta). Independent of NVD's CPE analysis and usually ahead of it.

• Okta Okta Verify for Windows

  • 5.0.2not affected
  • 5.0.1 and later · before 5.0.1affected · semver

Other highest-scoring records for the same primary product.

• CVE-2024-9191The Okta Device Access features, provided by the Okta Verify agent for Windows, provides access to the OktaDeviceAccessPipe, which enables a
  31Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1const file = path.join(ROOT, req.query.name);2res.sendFile(file);

1const file = path.resolve(ROOT, req.query.name);2if (!file.startsWith(ROOT + path.sep)) {3  return res.sendStatus(400);4}5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.