dbcve.org
Central Management SystemApplication · Trellix

CVE-2023-6072

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-13
Fix available
A fix is available. Upgrade to 9.1.3.97129 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
A cross-site scripting vulnerability in Trellix Central Management (CM) prior to 9.1.3.97129 allows a remote authenticated attacker to craft CM dashboard internal requests causing arbitrary content to be injected into the response when accessing the CM dashboard.

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

This is a stored cross-site scripting (XSS) vulnerability in Trellix Central Management (CM). An authenticated remote attacker can inject malicious content into CM dashboard internal requests, which then gets rendered when other users access the dashboard, allowing session hijacking or credential theft.

MitigationUpgrade Trellix Central Management to version 9.1.3.97129 or later to obtain the vendor patch. Additionally, implement Content Security Policy (CSP) headers as a defense-in-depth measure.

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
Central Management SystemApplication
Affected:< 9.1.3.97129

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
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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. Confirm Trellix CM deployment
    Identify whether Trellix Central Management is installed in your environment by reviewing running services, installed software listings, or accessing the CM web interface if known
    Affected if Trellix Central Management System is present in the environment
  2. Determine installed CM version
    Access the Trellix CM administrative console and locate the version information, typically found in Help > About, System > Status, or a similar administration page
    Affected if The installed version is lower than 9.1.3.97129
  3. Verify dashboard accessibility
    Confirm the CM dashboard is accessible to users by logging in and navigating to the main dashboard view that displays internal requests
    Affected if The dashboard is accessible and displays internal request data to authenticated users
  4. Inspect for injected content
    Review the CM dashboard for any unexpected or suspicious content in request fields, user-defined labels, or displayed parameters that may indicate prior exploitation
    Affected if Unexpected scripts or malicious content appear in dashboard-rendered fields

The environment is affected if Trellix Central Management version is below 9.1.3.97129 and the dashboard interface is accessible to authenticated users.

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

Upgrade Trellix Central Management to version 9.1.3.97129 or later to obtain the vendor patch. Additionally, implement Content Security Policy (CSP) headers as a defense-in-depth measure.

Recommended fix High confidence

9.1.3.97129 or later

  1. 1. Verify the current version of Trellix Central Management (CM) by accessing the CM dashboard and checking the system information or version display
  2. 2. If the version is below 9.1.3.97129, plan for an upgrade to version 9.1.3.97129 or later
  3. 3. Review Trellix upgrade documentation for CM to understand prerequisites and procedures
  4. 4. Create a backup of the current CM configuration as a precaution
  5. 5. Perform the upgrade to version 9.1.3.97129 or the latest available stable version following Trellix official upgrade procedures
  6. 6. After upgrade, verify the new version number in the CM dashboard
  7. 7. Test the CM dashboard functionality to ensure the upgrade was successful and the XSS vulnerability is remediated
Caveat Review Trellix release notes for version 9.1.3.97129 for any configuration or behavioral changes that may affect existing workflows

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

Fix this in Central Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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