dbcve.org
Enterprise Security ManagerApplication · Trellix

CVE-2024-11481

HIGH · 8.2 CVSS v3.1 Published 2024-11-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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
A vulnerability in ESM 11.6.10 allows unauthenticated access to the internal Snowservice API. This leads to improper handling of path traversal, insecure forwarding to an AJP backend without adequate validation, and lack of authentication for accessing internal API endpoints.

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 vulnerability in ESM 11.6.10 allows unauthenticated attackers to access the internal Snowservice API due to improper path traversal handling, insecure forwarding to an AJP backend without validation, and missing authentication on internal API endpoints.

MitigationApply vendor patch or upgrade to a fixed version; implement authentication enforcement on internal API endpoints and validate/sanitize path traversal inputs and AJP forwarding requests.

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.10

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/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. Verify ESM version
    Access the ESM administration console or check the installed software version through the system's 'About' or version information panel. Locate the exact version number displayed.
    Affected if The installed version is exactly 11.6.10 (Trellix Enterprise Security Manager)
  2. Check Snowservice API exposure
    Attempt to access the internal Snowservice API endpoint via HTTP/HTTPS request to the ESM server (e.g., /snowservice/* or similar internal API paths). Observe whether the request is accepted without requiring authentication credentials.
    Affected if The Snowservice API endpoint responds without requiring authentication or valid session credentials
  3. Inspect AJP connector configuration
    Locate and examine the AJP connector configuration files in the ESM deployment (typically in server.xml or similar configuration). Look for any forwarding rules or proxy settings to internal backends.
    Affected if AJP forwarding is enabled without validation rules, whitelist enforcement, or authentication checks on forwarded requests
  4. Review path traversal validation settings
    Examine the web application or proxy configuration for path traversal input validation. Check if URL parameters and request paths are validated against directory traversal patterns (such as ../ or absolute path references).
    Affected if Input validation for path traversal is absent or disabled in the web server or proxy configuration
  5. Confirm internal API authentication enforcement
    Review the API access control or authentication configuration for internal API endpoints. Test accessing internal API routes without providing valid authentication tokens or credentials.
    Affected if Internal API endpoints (including Snowservice API) do not enforce authentication or allow unauthenticated access

You are affected if running ESM version 11.6.10 and the Snowservice API or internal API endpoints are accessible without authentication due to missing validation on path traversal and AJP forwarding.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch or upgrade to a fixed version; implement authentication enforcement on internal API endpoints and validate/sanitize path traversal inputs and AJP forwarding requests.

Recommended fix Moderate confidence

Trellix ESM version newer than 11.6.10 (contact Trellix support for exact patched release)

  1. Check Trellix Enterprise Security Manager product updates and release notes at thrive.trellix.com for CVE-2024-11481
  2. Identify the patched version (look for version > 11.6.10 with security fix)
  3. Download and install the updated ESM version from the Trellix download portal
  4. After upgrade, verify the Snowservice API now requires proper authentication
  5. Confirm path traversal protections are in place by reviewing ESM configuration
Caveat Review ESM 11.6.10 to newer version migration guide for any configuration or compatibility considerations before upgrading

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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