CVE-2023-35080
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 vulnerability has been identified in the Ivanti Secure Access Windows client, which could allow a locally authenticated attacker to exploit a vulnerable configuration, potentially leading to various security risks, including the escalation of privileges, denial of service, or information disclosure.
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 locally authenticated attacker can exploit a vulnerable configuration in the Ivanti Secure Access Windows client to potentially escalate privileges to higher levels, cause denial of service, or disclose sensitive information. The vulnerability requires the attacker to have valid local credentials on the target Windows system.
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.6= 22.6CVSS 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
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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.
-
Check Ivanti Secure Access Client versionOpen Windows Control Panel > Programs and Features, or use PowerShell command Get-ItemProperty to query the installed version of Ivanti Secure Access ClientAffected if Version is lower than 22.6 or equals 22.6
-
Verify the vulnerable configuration is enabledReview Ivanti Secure Access Client configuration files or settings that control local authentication and privilege escalation behaviorAffected if The vulnerable configuration setting is present or enabled in the client settings
-
Confirm local user authentication is permittedCheck Ivanti Secure Access Client settings to verify whether local credential authentication is allowed on the systemAffected if Local user authentication is enabled and the attacker can obtain valid local credentials
Environment is affected if Ivanti Secure Access Client version is 22.6 or lower and the vulnerable configuration setting is enabled, allowing a locally authenticated attacker to escalate privileges
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.6
Apply the vendor-supplied patch or update to Ivanti Secure Access client; review and harden client configurations to eliminate the vulnerable configuration settings.
22.7 or later
- Download Ivanti Secure Access Client version 22.7 or later from the official Ivanti download portal
- Ensure you have administrator privileges on the Windows machine
- Uninstall the current version of Ivanti Secure Access Client via Windows Settings > Apps or using the uninstaller
- Restart the Windows machine after uninstallation
- Install the new version (22.7 or later) of Ivanti Secure Access Client with default installation settings
- Verify the installation completed successfully and the client is running
- Restart the machine if prompted to complete the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35080 — 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-35080 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