Advanced Server AccessApplication · Okta

CVE-2023-0093

HIGH · 8.8 CVSS v3.1 Published 2023-03-06
Fix available
A fix is available. Upgrade to 1.68.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Advanced Server Access Client versions 1.13.1 through 1.65.0 are vulnerable to command injection due to the third party library webbrowser. An outdated library, webbrowser, used by the ASA client was found to be vulnerable to command injection. To exploit this issue, an attacker would need to phish the user to enter an attacker controlled server URL during enrollment.

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

The Okta Advanced Server Access Client uses an outdated version of the Python webbrowser library which is vulnerable to command injection. During the enrollment process, the client uses this library to handle server URLs, and an attacker can inject malicious commands through a specially crafted URL that gets executed by the webbrowser library's underlying system calls.

MitigationUpdate Okta Advanced Server Access Client to version 1.65.1 or later, which includes a patched version of the webbrowser library. As a temporary measure, users should not enter untrusted or attacker-controlled server URLs during enrollment.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Advanced Server AccessApplication
Affected:>= 1.13.1, < 1.68.2

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Check if Okta Advanced Server Access Client is installed
    Look for the client executable on the system. On Windows, check Program Files for 'Okta ASA Client' or run 'asa-client --version' if in PATH. On macOS, check /Applications or run the version command. On Linux, check common installation directories or use which asa-client.
    Affected if The client executable is found on the system.
  2. Determine the installed version number
    Run the client with version flag: 'asa-client --version' or 'asa-client -v', or right-click the application and select About/Properties to view the version.
    Affected if A version number is returned that falls within the range >= 1.13.1 and < 1.68.2.
  3. Verify enrollment feature accessibility
    Check if the client has been used for enrollment or if enrollment functionality is available. Look for enrollment-related logs, configuration files, or recent enrollment activity.
    Affected if Enrollment has been performed or could be initiated with a server URL.
  4. Inspect recent enrollment URLs or server configurations
    Review client logs in the application data directory for any server URLs entered during enrollment. Check configuration files for stored server connections.
    Affected if Server URLs were entered during enrollment on an affected version.

A user is affected if Okta Advanced Server Access Client version is >= 1.13.1 and < 1.68.2, and the enrollment feature with server URL input has been used.

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
Upgrade available Upgrade to 1.68.2 or later
Fixed in 1.68.2
Interim mitigation

Update Okta Advanced Server Access Client to version 1.65.1 or later, which includes a patched version of the webbrowser library. As a temporary measure, users should not enter untrusted or attacker-controlled server URLs during enrollment.

Recommended fix High confidence

1.68.2

  1. Upgrade Okta Advanced Server Access Client to version 1.68.2 or later

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

Fix this in Advanced Server Access Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0093 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2023-0093 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