dbcve.org
Deep Security AgentApplication · Trendmicro

CVE-2025-30642

MEDIUM · 5.5 CVSS v3.1 Published 2025-06-17
Fix available
A fix is available. Upgrade to 20.0.1 or later.
See remediation →
57/100
Remediation priority · Elevated
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.0 agents could allow a local attacker to create a denial of service (DoS) situation 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 · moderate confidence

A link following (symlink attack) vulnerability in Trend Micro Deep Security Agent 20.0 allows a local attacker with low-privileged code execution to create symlinks that the agent follows, leading to denial of service. The vulnerability stems from improper validation of file paths before operations, enabling manipulation of file system references.

MitigationApply the vendor-supplied patch for Deep Security Agent 20.0. Additionally, restrict file system access for low-privileged accounts and monitor for suspicious symlink creation in agent directories as a compensating control until patching is complete.

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= 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
    Check for the presence of Deep Security Agent on the system using system inventory tools or package managers (for example, 'Get-ItemProperty' in PowerShell or 'wmic product' on Windows, or 'rpm -qa' or 'dpkg -l' on Linux)
    Affected if Deep Security Agent version 20.0.x is found on the system
  2. Determine installed agent version
    Query the installed version of the Deep Security Agent using the vendor's recommended method, such as the agent's system tray icon, command-line utility, or registry/system information
    Affected if The displayed version is 20.0 or 20.0.1 specifically
  3. Compare version against affected range
    Compare your installed version number to the affected range: versions less than 20.0.1 (such as 20.0.0) or exactly version 20.0.1 are vulnerable; version 20.0.2 and later are patched
    Affected if The installed version is 20.0 or 20.0.1, meaning it falls within the < 20.0.1 or = 20.0.1 affected range
  4. Identify agent process and directories
    Locate the running Deep Security Agent process and its installation directory using system monitoring tools or process inspection commands
    Affected if The agent process (typically named 'ds_agent' or similar) is running from a directory that low-privileged users can access for file creation

You are affected if Deep Security Agent version 20.0 or 20.0.1 is installed on your system, as these versions contain the symlink vulnerability due to improper file path validation.

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

Apply the vendor-supplied patch for Deep Security Agent 20.0. Additionally, restrict file system access for low-privileged accounts and monitor for suspicious symlink creation in agent directories as a compensating control until patching is complete.

Recommended fix Moderate confidence

Deep Security Agent 20.0.2 or later

  1. Navigate to the Trend Micro Deep Security download center or contact Trend Micro support for the latest agent package
  2. Download Deep Security Agent version 20.0.2 or later
  3. Deploy and install the updated agent on affected systems using your standard deployment method (e.g., manual installation, MSI package, or management console push)
  4. Verify the agent version post-installation to confirm the patch was applied

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

Fix this in Deep Security Agent Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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