Cyber Resilience

CVE-2023-32556

Trendmicro Apex One ≤ 14.0.12105

Published
26 June 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0029 21th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2023-32556 is a medium-severity Link Following (CWE-59) vulnerability in Trendmicro Apex One. Its CVSS base score is 5.5 (Medium).

Operationally, ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

A link following vulnerability in the Trend Micro Apex One and Apex One as a Service agent could allow a local attacker to disclose sensitive information. Please note: an attacker must first obtain the ability to execute low-privileged code on…

more

the target system in order to exploit this vulnerability.

CWE(s)
CWE-59

Related Threats

CVEs Like This One

CVE-2023-25145Same product: Microsoft Windows
CVE-2023-25148Same product: Microsoft Windows
CVE-2023-25146Same product: Microsoft Windows
CVE-2023-34147Same product: Microsoft Windows
CVE-2023-30902Same product: Microsoft Windows
CVE-2023-32552Same product: Microsoft Windows
CVE-2023-32555Same product: Microsoft Windows
CVE-2023-25147Same product: Microsoft Windows
CVE-2023-25144Same product: Microsoft Windows
CVE-2023-34144Same product: Microsoft Windows

Affected Assets

trendmicro
apex one
2019 · ≤ 14.0.12105

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.4.2

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require code to validate paths and avoid unsafe link following.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can detect link-following flaws before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC practices can mandate link-resolution checks and canonicalization before file access.

A.8.26 Application security requirements partial match
prevents

Application security requirements can explicitly require safe handling of symbolic links and path traversal.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include input validation and safe file-access design patterns.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address canonicalization and symlink attacks during implementation.

A.8.3 Information access restriction none match
none

Access-control rules can limit which files are reachable, reducing exposure to malicious links.

References