CVE-2024-13813
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 · uneditedInsufficient permissions in Ivanti Secure Access Client before version 22.8R1 allows a local authenticated attacker to delete arbitrary files.
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 confidenceIvanti Secure Access Client before version 22.8R1 contains insufficient permission checks that allow a locally authenticated attacker to delete arbitrary files on the filesystem. This local privilege escalation vulnerability could enable denial of service or be chained with other attacks.
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.8CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Verify Ivanti Secure Access Client is installedOn Windows, check Add/Remove Programs or search for 'Ivanti Secure Access Client' in the system. On Linux, check installed packages with 'dpkg -l | grep -i ivanti' or 'rpm -qa | grep -i ivanti'.Affected if The software is not found on the system, indicating it is not installed and therefore not affected by this vulnerability.
-
Determine the installed version numberRun the client binary with version flag, such as 'IvantiSecureAccessClient --version' or check the executable properties. On Windows, right-click the executable and select Properties > Details to view the File Version.Affected if The detected version is less than 22.8R1 (or 22.8), placing it within the vulnerable version range.
-
Confirm the service or daemon is runningOn Windows, open Services and look for 'Ivanti Secure Access Client' service, or run 'sc query IvantiSecureAccessClient'. On Linux, run 'systemctl status ivanti-secure-access' or check running processes for the client binary.Affected if The service is running and the version is below 22.8R1, indicating the vulnerable configuration is active.
-
Check if local user authentication is enabledReview the client configuration or group policy settings that control local user authentication methods. This may be in the client UI under Authentication settings or in configuration files.Affected if Local user authentication is enabled and the client version is below 22.8R1, enabling the attack vector described in the CVE.
A system is affected if Ivanti Secure Access Client is installed with a version lower than 22.8R1 and the service is running with local authentication capabilities available.
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.8
Upgrade Ivanti Secure Access Client to version 22.8R1 or later to obtain the patched version with proper permission controls.
22.8R1 or later
- Obtain the Ivanti Secure Access Client version 22.8R1 or later from the official Ivanti download portal or through your existing support channel
- Review the Ivanti upgrade documentation for Secure Access Client
- Backup current client configuration if applicable
- Deploy the updated Secure Access Client version 22.8R1 or newer to affected systems
- Verify the installation completed successfully and the version number reflects 22.8R1 or later
- Test that the VPN connection functionality remains operational after the upgrade
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-2024-13813 — 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-2024-13813 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