dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2023-39336

HIGH · 8.8 CVSS v3.1 Published 2024-01-09
Fix available
A fix is available. Upgrade to 2022 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

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 · unedited
An unspecified SQL Injection vulnerability in Ivanti Endpoint Manager released prior to 2022 SU 5 allows an attacker with access to the internal network to execute arbitrary SQL queries and retrieve output without the need for authentication. Under specific circumstances, this may also lead to RCE on the core server.

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 confidence

An unauthenticated SQL injection vulnerability in Ivanti Endpoint Manager (versions prior to 2022 SU 5) allows attackers on the internal network to execute arbitrary SQL queries without authentication. Under specific conditions, this can escalate to remote code execution on the core server.

MitigationUpgrade Ivanti Endpoint Manager to version 2022 SU 5 or later. If immediate patching is not feasible, strictly limit network access to the affected system and implement additional network segmentation controls.

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
Endpoint ManagerApplication
Affected:< 2022= 2022

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Ivanti Endpoint Manager version
    Access the Ivanti Endpoint Manager console or check the product's About/Version information panel. Alternatively, locate the installation directory and check version metadata files if accessible.
    Affected if The installed version is 2022 (any build) or any version prior to 2022 SU 5, meaning it falls within the '< 2022; = 2022' range.
  2. Confirm the specific 2022 build number
    Within the product interface or version documentation, identify the exact build or service pack level (such as SU1, SU2, SU3, SU4, or SU5).
    Affected if The build is earlier than SU5 (for example, 2022 SU4, SU3, SU2, SU1, or base 2022 release), indicating the vulnerability is present.
  3. Determine network exposure of the EPM server
    Review firewall rules, network ACLs, or VLAN configuration to identify whether the Ivanti Endpoint Manager server is reachable from internal network segments or only from dedicated admin workstations.
    Affected if The server listens on ports accessible to general internal network users (not restricted to admin-only IP ranges), creating the condition for unauthenticated internal attackers to reach the vulnerable endpoint.
  4. Inspect web access logs for SQL injection patterns
    Examine IIS logs, Apache logs, or application logs for the EPM web interface looking for SQL meta-characters (such as single quotes, UNION SELECT, OR 1=1, xp_cmdshell) in query parameters.
    Affected if Suspicious SQL injection payloads appear in the logs, indicating potential exploitation attempts against the vulnerability.
  5. Verify database account privileges
    Check the database connection configuration used by the EPM application. Determine if the application database account has elevated privileges such as sysadmin or db_owner that could enable xp_cmdshell or similar procedures.
    Affected if The EPM service account has excessive database privileges, meaning successful SQL injection could escalate to command execution.

You are affected if your Ivanti Endpoint Manager version is 2022 (any build) or any version before 2022 SU 5, and the server is accessible from your internal network without strict IP-based access controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2022 or later
Fixed in 2022
Interim mitigation

Upgrade Ivanti Endpoint Manager to version 2022 SU 5 or later. If immediate patching is not feasible, strictly limit network access to the affected system and implement additional network segmentation controls.

Recommended fix Moderate confidence

2022 SU 5 or later

  1. Identify the current version of Ivanti Endpoint Manager installed on the server
  2. Obtain the 2022 SU 5 (or later) update package from the official Ivanti download portal or through your licensed support channel
  3. Review the Ivanti Endpoint Manager upgrade documentation for prerequisites and compatibility checks
  4. Backup the current Endpoint Manager database and configuration
  5. Apply the 2022 SU 5 update following the standard Ivanti update procedure
  6. Verify the upgrade was successful by checking the version in the admin console
  7. Test critical functionality to ensure the update did not disrupt normal operations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-39336 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-39336 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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