dbcve.org
Deep Security AgentApplication · Trendmicro

CVE-2024-51503

HIGH · 8.8 CVSS v3.1 Published 2024-11-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 security agent manual scan command injection vulnerability in the Trend Micro Deep Security 20 Agent could allow an attacker to escalate privileges and execute arbitrary code on an affected machine. In certain circumstances, attackers that have legitimate access to the domain may be able to remotely inject commands to other machines in the same domain. Please note: an attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability locally and must have domain user privileges to affect other machines.

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

Command injection vulnerability in Trend Micro Deep Security 20 Agent's manual scan feature allows authenticated attackers with low-privileged code execution to escalate to SYSTEM privileges and execute arbitrary code. Attackers with domain user privileges can also inject commands laterally to other machines in the same domain.

MitigationApply the vendor security update/patch for Deep Security Agent 20 to remediate the command injection vulnerability. Prioritize patching agents on high-privilege systems and domain controllers.

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

CVSS:3.1/AV:N/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 the installed Deep Security Agent version
    Check the installed version of Trend Micro Deep Security Agent through the Windows Registry at HKLM\SOFTWARE\TrendMicro\Deep Security Agent\InstallPath or by running 'msiexec /x' on the installed MSI, or use 'dsm -v' command if available
    Affected if The installed version is exactly 20.0 or 20.0.1
  2. Confirm the agent service is running
    Check if the Trend Micro Deep Security Agent service (ds_agent) is running on the system using Services.msc or the command 'sc query ds_agent'
    Affected if The agent service is running and the version check shows 20.0 or 20.0.1
  3. Verify manual scan functionality is accessible
    Check if the manual scan feature is enabled in the Deep Security Agent policy or configuration. This can be verified through the Deep Security Manager console or by inspecting the agent configuration files in the installation directory
    Affected if Manual scan is enabled on an affected version (20.0 or 20.0.1)
  4. Review agent audit and event logs for suspicious scan activity
    Examine Deep Security Agent logs for unexpected or unauthorized scan commands, particularly those originating from low-privilege or domain user contexts. Logs are typically stored in the agent's log directory
    Affected if Logs show scan commands initiated by unexpected users or processes on affected versions

A system is affected if it runs Trend Micro Deep Security Agent versions 20.0 or 20.0.1 and has the manual scan feature enabled or accessible.

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 the vendor security update/patch for Deep Security Agent 20 to remediate the command injection vulnerability. Prioritize patching agents on high-privilege systems and domain controllers.

Recommended fix Moderate confidence

Deep Security Agent 20.0.2 or later (recommended: latest 20.x release)

  1. Identify the current Deep Security Agent version installed on affected systems using the agent status command or console
  2. Download Deep Security Agent version 20.0.2 or later from the Trend Micro Download Center
  3. Test the upgrade in a non-production environment first
  4. Deploy the upgrade using your standard deployment method (push install, MSI package, or manual installation)
  5. Verify the agent is running the fixed version post-upgrade
  6. Confirm normal scanning functionality works as expected

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

Fix this in Deep Security Agent Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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