Cyber Resilience

CVE-2023-32557

Path Traversal in Trendmicro Apex One ≤ 14.0.12105

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

Summary

CVE-2023-32557 is a critical-severity Path Traversal (CWE-22) vulnerability in Trendmicro Apex One. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 34% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

A path traversal vulnerability tracked as CVE-2023-32557 affects Trend Micro Apex One and Apex One as a Service. The flaw, assigned CWE-22 and carrying a CVSS 3.1 score of 9.8, resides in the Management Server and enables an unauthenticated attacker to upload an arbitrary file.

An unauthenticated remote attacker can exploit the issue over the network with no credentials or user interaction required, achieving remote code execution with system privileges on the Management Server.

Vendor advisory information addressing the vulnerability is available at the Trend Micro success portal links referenced for this CVE. The associated EPSS score has remained flat at its peak value of 0.0643 with no material increase observed.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A path traversal vulnerability in the Trend Micro Apex One and Apex One as a Service could allow an unauthenticated attacker to upload an arbitrary file to the Management Server which could lead to remote code execution with system privileges.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2019-18187Same product: Microsoft Windows
CVE-2025-71211Same product: Trendmicro Apex One
CVE-2025-71210Same product: Trendmicro Apex One
CVE-2024-24749Same product: Microsoft Windows
CVE-2024-7263Same product: Microsoft Windows
CVE-2025-63372Same product: Microsoft Windows
CVE-2025-11001Same product: Microsoft Windows
CVE-2024-42474Same product: Microsoft Windows
CVE-2023-41747Same product: Microsoft Windows
CVE-2023-4593Same 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)
  • V5.3.2

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-22

Validates pathnames and filenames to prevent traversal outside intended directories.

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-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

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.

finds

Security testing in development catches path traversal via static/dynamic analysis.

prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

prevents

Application security requirements include rules for safe file handling and canonicalization.

prevents

Secure architecture principles require least-privilege file access and directory isolation.

prevents

Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.

mitigates

Information access restriction limits which files an application may read or write.

References