CVE-2024-36306
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 · uneditedA link following vulnerability in the Trend Micro Apex One and Apex One as a Service Damage Cleanup Engine could allow a local attacker to create a denial-of-service condition 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 confidenceA link following (symlink) vulnerability in Trend Micro Apex One and Apex One as a Service Damage Cleanup Engine allows a local attacker with low-privileged code execution to create a denial-of-service condition by manipulating symbolic links that the cleanup engine follows.
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>= 14.0, < 14.0.0.12980CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Apex One installationLocate and verify Trend Micro Apex One software is installed on the system using standard software inventory or program listing methodsAffected if Apex One is not present on the system
-
Identify installed Apex One versionRetrieve the installed version number of the Apex One client or server componentAffected if The installed version is >= 14.0 and < 14.0.0.12980
-
Verify Damage Cleanup Engine componentCheck whether the Damage Cleanup Engine component is present and active within the Apex One installationAffected if The Damage Cleanup Engine is installed and enabled
-
Inspect cleanup engine directory permissionsExamine directories accessed by the Damage Cleanup Engine for symlink creation opportunities by low-privileged usersAffected if Low-privileged users can create or manipulate symbolic links in directories accessed by the cleanup service
The environment is affected if Apex One version is 14.0 or higher but below 14.0.0.12980 AND the Damage Cleanup Engine component is present and accessible to low-privileged users for symlink manipulation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped14.0.0.12980
Apply vendor-supplied security patches for the Apex One Damage Cleanup Engine component and review system permissions to limit symlink creation in directories accessed by the cleanup service.
Apex One version 14.0.0.12980 or later
- 1. Ensure you have a backup of your current Apex One installation and data.
- 2. Download the latest version of Trend Micro Apex One from the official Trend Micro download center or your licensed channel.
- 3. Apply the upgrade following Trend Micro's standard upgrade procedure for Apex One.
- 4. Verify the upgrade was successful by checking the Apex One console version information.
- 5. Confirm the Damage Cleanup Engine is functioning normally after the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36306 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-36306 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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