dbcve.org
Deep Security AgentApplication · Trendmicro

CVE-2024-36358

HIGH · 7.8 CVSS v3.1 Published 2024-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A link following vulnerability in Trend Micro Deep Security 20.x agents below build 20.0.1-3180 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 link following (symlink) vulnerability in Trend Micro Deep Security 20.x agent builds prior to 20.0.1-3180 allows a local attacker with low-privileged code execution to escalate to administrator/root privileges by exploiting how the agent handles symbolic links during file operations.

MitigationUpdate Trend Micro Deep Security agents to build 20.0.1-3180 or later to patch the vulnerability.

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
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. Verify Deep Security Agent is installed
    Locate the Deep Security Agent installation on the system. Common locations include C:\Program Files\Trend Micro\Deep Security Agent on Windows or /opt/ds_agent on Linux. Check for the presence of the agent executable or service.
    Affected if The Deep Security Agent software is present on the system
  2. Identify the installed agent build version
    Query the agent for its version information. On Windows, this can often be done via the system tray icon, the dsamain process properties, or running 'dsm -v' from the installation directory. On Linux, try '/opt/ds_agent/dsa -v' or check the agent logs in /var/log/ds_agent/. The version is displayed as a build number.
    Affected if The command returns a build number lower than 20.0.1-3180
  3. Confirm the exact version string
    Review the complete version string returned, which typically follows the format like 20.0.0-XXXX or 20.0.1-XXXX where XXXX represents the build number. Ensure you capture the full build identifier including the hyphenated build suffix.
    Affected if The version shows 20.0.1 with build less than 3180, or shows 20.0.0 at any build

The system is affected if the Deep Security Agent is installed and the version/build number is 20.0.0 at any build or 20.0.1 with a build number lower than 3180.

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 Trend Micro Deep Security agents to build 20.0.1-3180 or later to patch the vulnerability.

Recommended fix High confidence

Deep Security Agent 20.0.1-3180 or later

  1. Obtain the fixed Deep Security Agent package (build 20.0.1-3180 or later) from the Trend Micro customer portal or official download channels
  2. Backup the current agent configuration and any relevant policy settings
  3. Stop the Deep Security Agent service before upgrading
  4. Install the updated agent package using the standard installation method (msi installer for Windows or package manager for Linux)
  5. Verify the agent version after installation matches the fixed build (20.0.1-3180 or higher)
  6. Restart the agent service and confirm normal operation
  7. Verify that security policies and protections are functioning as expected
Caveat Review Trend Micro release notes for any policy or configuration changes between your current version and 20.0.1-3180

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-36358 — 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-36358 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