CVE-2024-11772
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 · uneditedCommand injection in the admin web console of Ivanti CSA before version 5.0.3 allows a remote authenticated attacker with admin privileges to achieve remote code execution.
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 confidenceA command injection vulnerability exists in the admin web console of Ivanti Connect Secure (CSA) before version 5.0.3. An authenticated attacker with admin privileges can inject arbitrary commands through the web interface, leading to remote code execution on the underlying 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< 5.0.3CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Identify Ivanti CSA versionLog into the admin web console and navigate to the System Configuration or About section to view the installed version. Alternatively, check the appliance's system information page or login banner which typically displays the version.Affected if The displayed version is lower than 5.0.3 (for example, 5.0.2, 5.0.1, or earlier releases).
-
Confirm admin web console is accessibleVerify that the Ivanti Connect Secure admin interface is reachable over the network on the default HTTPS port (usually 443 or 8443). Attempt to access the admin login page.Affected if The admin console is exposed to the network without IP restrictions.
-
Verify admin account accessConfirm that valid admin credentials exist on the system. Check if default admin accounts are enabled or if additional administrative users have been created.Affected if An authenticated admin user can log in to the web interface.
-
Assess network exposure of admin interfaceReview firewall rules, access control lists, or VPN configurations that govern who can reach the admin web console. Determine if it is accessible from untrusted networks.Affected if The admin console is accessible from the internet or untrusted internal networks.
A system is affected if the installed Ivanti CSA version is below 5.0.3 and the admin web console is accessible to an authenticated attacker with admin 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 · scoped5.0.3
Upgrade Ivanti CSA to version 5.0.3 or later. Until patched, restrict admin console access to trusted IP addresses only and closely monitor for suspicious admin activity.
5.0.3
- Back up the current Ivanti CSA configuration and any critical data
- Download Ivanti CSA version 5.0.3 or later from the official Ivanti support portal (forums.ivante.com)
- Follow the official Ivanti upgrade documentation for the CSA appliance
- After upgrade, verify the version number matches 5.0.3 or later in the admin web console
- Confirm the admin web console is accessible and functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11772 — 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-11772 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