dbcve.org
Enterprise Security ManagerApplication · Trellix

CVE-2023-3313

HIGH · 7.8 CVSS v3.1 Published 2023-07-03
Fix available
A fix is available. Upgrade to 11.6.7 or later.
See remediation →
80/100
Remediation priority · High
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 OS common injection vulnerability exists in the ESM certificate API, whereby incorrectly neutralized special elements may have allowed an unauthorized user to execute system command injection for the purpose of privilege escalation or to execute arbitrary commands.

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 confidence

A command injection vulnerability exists in the ESM certificate API where improperly sanitized user input in certificate processing allows attackers to inject OS commands. This could enable privilege escalation from an unauthorized user context or execution of arbitrary system commands.

MitigationImplement strict input validation and use parameterized APIs or safe library functions instead of passing user-controlled data to system command execution functions. Apply principle of least privilege to the certificate processing service.

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
Enterprise Security ManagerApplication
Affected:< 11.6.7

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
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 checks

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

  1. Identify if Trellix Enterprise Security Manager is installed
    Locate the ESM installation directory or check system services for 'Trellix' or 'ESM' processes. Common paths may include C:\Program Files\Trellix\ESM or /opt/trellix/esm.
    Affected if Trellix Enterprise Security Manager software is present on the system
  2. Determine the installed ESM version
    Check the ESM version through the product interface, About dialog, or version file in the installation directory. Look for a version file named version.ini, version.txt, or check the Windows registry under HKLM\SOFTWARE\Trellix\ESM for the Version value.
    Affected if The installed version is lower than 11.6.7 (e.g., 11.5.x, 11.4.x, etc.)
  3. Verify the ESM certificate API is accessible
    Check if the ESM certificate API endpoint is exposed or enabled. This may be configurable in the ESM management console under API settings, or check for certificate-related service ports responding.
    Affected if The certificate API is enabled and accessible to the user in question
  4. Inspect certificate processing configuration
    Review ESM configuration files related to certificate handling, typically found in the config subdirectory of the ESM installation. Look for files named cert.ini, certificate.xml, or similar that define certificate processing behavior.
    Affected if Certificate processing is configured with user-controlled input paths or parameters without sanitization

A system is affected if Trellix Enterprise Security Manager version 11.6.7 or lower is installed with the certificate API enabled and certificate processing configured to accept user input.

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 11.6.7 or later
Fixed in 11.6.7
Interim mitigation

Implement strict input validation and use parameterized APIs or safe library functions instead of passing user-controlled data to system command execution functions. Apply principle of least privilege to the certificate processing service.

Recommended fix High confidence

11.6.7

  1. Verify current Enterprise Security Manager version through the ESM web interface or command line interface
  2. Download the ESM 11.6.7 update package from the official Trellix support portal at kcm.trellix.com
  3. Review release notes for any pre-upgrade requirements or migration procedures
  4. Execute the upgrade following the standard ESM upgrade process documented in the Trellix installation guide
  5. Verify successful installation by confirming the ESM version displays as 11.6.7 or later
  6. Test that the ESM certificate API functionality operates normally after the upgrade

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

Fix this in Enterprise Security Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3313 — 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-3313 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