CVE-2024-36306 json
A link following vulnerability in the Trend Micro Apex One and Apex One as a Service Damage Cleanup Engine could allow a local attacker to…
published 2y ago modified 4mo ago also EUVD-2024-36025
- cvss
- 6.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 49%
- public exploits
- 0
- none known
Summary
A 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.
Patch / fix
- Trend Micro, Inc. Trend Micro Apex One 14.0.0.12980
- Trend Micro, Inc. Trend Micro Apex One as a Service 14.0.13139
Is CVE-2024-36306 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Trend Micro, Inc. Trend Micro Apex One
- Trend Micro, Inc. Trend Micro Apex One as a Service
Classification
- Weakness
-
- CWE-59 Improper Link Resolution Before File Access
References
-
success.trendmicro.com
/dcx/s/solution/000298063
broken-link
-
zerodayinitiative.com
/advisories/ZDI-24-568/
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2024-36306
- NVD CVE-2024-36306
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.