Skip to content
Fencer Intel
medium 4.7

CVE-2024-36307 json

A security agent link following vulnerability in Trend Micro Apex One and Apex One as a Service could allow a local attacker to disclose se…

published 2y ago modified 4mo ago also EUVD-2024-36026

cvss
4.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

A security agent link following vulnerability in Trend Micro Apex One and Apex One as a Service could allow a local attacker to disclose sensitive information about the agent 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
  • trendmicro apex_one 14.0.0.12980, 14.0.13139

Is CVE-2024-36307 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 Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.78% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected products

  • Trend Micro, Inc. Trend Micro Apex One
  • Trend Micro, Inc. Trend Micro Apex One as a Service
  • trendmicro apex_one

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

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.