dbcve.org
Deep Security AgentApplication · Trendmicro

CVE-2024-55955

HIGH · 7.3 CVSS v3.1 Published 2024-12-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated

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 incorrect permissions assignment vulnerability in Trend Micro Deep Security 20.0 agents between versions 20.0.1-9400 and 20.0.1-23340 could allow a local attacker to escalate privileges on affected installations. Please note: an attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.

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

A local privilege escalation vulnerability exists in Trend Micro Deep Security 20.0 agents due to incorrect permissions assignment on certain files, directories, or services. An attacker with low-privileged code execution can exploit improper access controls to gain SYSTEM or administrator-level privileges on affected installations.

MitigationUpdate Deep Security agents to version 20.0.1-23340 or later. Apply the vendor patch to remediate the permissions misconfiguration.

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
Deep Security AgentApplication
Affected:= 20.0.1

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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. Confirm Deep Security Agent is installed
    Locate the Deep Security Agent on the system using system inventory tools, process lists, or installed software enumeration
    Affected if The Deep Security Agent is not found on the system
  2. Retrieve the installed agent version
    Use system-appropriate commands to query the Deep Security Agent version (such as checking the agent service information, registry keys on Windows, or package management on Linux)
    Affected if The exact version cannot be determined or the agent is not present
  3. Compare version against CVE-affected range
    Match the retrieved version number to the affected version specified in the CVE: version 20.0.1
    Affected if The installed version is exactly 20.0.1 and has not been patched to version 20.0.1-23340 or later

A system is affected only if the Deep Security Agent version installed is exactly 20.0.1 and the security patch (20.0.1-23340 or later) has not been applied.

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

Update Deep Security agents to version 20.0.1-23340 or later. Apply the vendor patch to remediate the permissions misconfiguration.

Recommended fix Moderate confidence

Deep Security Agent 20.0.1 version higher than 20.0.1-23340 (latest available 20.0.1 build)

  1. 1. Identify the exact version of Deep Security Agent installed (check via 'dsm_cli -v' or the Deep Security Manager console)
  2. 2. Verify the current version falls within the affected range: 20.0.1-9400 to 20.0.1-23340
  3. 3. Contact Trend Micro customer support or access the Trend Micro Download Center to obtain the latest Deep Security Agent 20.0.1 build that includes the security fix
  4. 4. Test the upgrade in a non-production environment first
  5. 5. Apply the upgrade following standard Deep Security Agent deployment procedures
  6. 6. Verify the agent is running the patched version after upgrade
Caveat Review Trend Micro release notes for any configuration or compatibility changes between versions

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

Fix this in Deep Security Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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