CVE-2024-37381
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 · uneditedAn unspecified SQL Injection vulnerability in Core server of Ivanti EPM 2024 flat allows an authenticated attacker within the same network to execute arbitrary code.
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 confidenceSQL injection vulnerability in the Core server component of Ivanti EPM 2024 allows authenticated attackers with network access to inject malicious SQL queries that can lead to arbitrary 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= 2024CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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.
-
Confirm Ivanti Endpoint Manager installationCheck for Ivanti Endpoint Manager (EPM) installation on the system. Look for the application in installed programs (Windows) or check for the EPM installation directory, typically found under C:\Program Files\Ivanti or similar paths.Affected if Ivanti Endpoint Manager 2024 is installed on the system
-
Verify the exact version numberLocate the version information for the installed Ivanti EPM instance. This can typically be found in the application itself (Help > About), in the Windows registry under HKLM\SOFTWARE\Ivanti, or in an about/info file within the installation directory.Affected if The installed version is exactly 2024 (not a later patched version)
-
Identify if Core server component is activeCheck if the Core server component is running or enabled. This is typically visible in the Ivanti EPM admin console under Server Components, or can be checked via Windows Services looking for 'Ivanti Endpoint Manager Core' or similar service names.Affected if The Core server component is installed and running
-
Determine network exposureAssess whether the Core server is accessible over the network. Check firewall rules, listening ports (typically port 8080 or 443 for EPM), and network configuration to determine if the server accepts remote connections.Affected if The Core server component is network-accessible from untrusted networks
-
Verify authentication configurationCheck if user authentication is enabled and configured for the EPM server. Examine the authentication methods allowed (Windows authentication, LDAP, local accounts) and whether guest or anonymous access is permitted.Affected if User authentication is configured and accessible to the attacker
The environment is affected if Ivanti Endpoint Manager version 2024 is installed with the Core server component enabled and accessible over the network to authenticated users.
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.
From vendor dataImplement parameterized queries/prepared statements for all database operations, apply input validation and sanitization on user-supplied data, and restrict database permissions to least privilege.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37381 — 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-37381 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