CVE-2023-46810
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 · uneditedA local privilege escalation vulnerability in Ivanti Secure Access Client for Linux before 22.7R1, allows a low privileged user to execute code as root.
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 confidenceA local privilege escalation vulnerability in Ivanti Secure Access Client for Linux versions prior to 22.7R1 allows an authenticated low-privileged user to elevate privileges to root by executing arbitrary code through improper privilege management in the client software.
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< 22.7CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Ivanti Secure Access Client is installedRun 'dpkg -l | grep -i ivanti' or 'rpm -qa | grep -i ivanti' depending on your package manager, or check for /opt/ivanti directoryAffected if The package or directory is present on the system
-
Retrieve the installed version numberRun 'dpkg -l ivanti-secure-access-client' or 'rpm -q ivanti-secure-access-client', or use the --version flag with the client binary if located in /opt/ivanti/bin/Affected if The version returned is lower than 22.7R1 or the command fails to show version 22.7 or later
-
Confirm the client is the Linux versionCheck the package name includes 'linux' or the binary is confirmed to run on Linux OS (uname -a)Affected if The client is the Linux version and version is below 22.7R1
-
Verify the vulnerability precondition existsCheck if the client is configured to allow authenticated users (run 'ls -la /opt/ivanti/etc/' or similar to inspect client configuration files for user permissions)Affected if Low-privileged user accounts are permitted to authenticate to the client
A user is affected if Ivanti Secure Access Client for Linux is installed with a version lower than 22.7R1 and allows authenticated low-privileged access.
Generated from the published advisory. Verify against your own configuration.
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 · scoped22.7
Upgrade Ivanti Secure Access Client for Linux to version 22.7R1 or later to remediate this vulnerability.
22.7R1
- 1. Back up the current Ivanti Secure Access Client configuration
- 2. Download the Ivanti Secure Access Client version 22.7R1 or later from the official Ivanti download portal
- 3. Uninstall the current version of Ivanti Secure Access Client: sudo apt-get remove ivanti-secure-access-client or sudo rpm -e ivanti-secure-access-client
- 4. Install the new version: sudo apt-get install ./ivanti-secure-access-client-22.7R1.x86_64.rpm or sudo dpkg -i ./ivanti-secure-access-client-22.7R1.x86_64.deb
- 5. Verify the installation completed successfully and the service is running
- 6. Confirm the version number matches 22.7R1 or later using the client or command line tool
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46810 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-46810 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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