Cyber Resilience

CVE-2024-52885

Path Traversal in Checkpoint Mobile Access

Published
06 August 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 5.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
EPSS Score 0.0046 37th percentile
Risk Priority 39 floored blend · peak EPSS

Summary

CVE-2024-52885 is a medium-severity Path Traversal: '.../...//' (CWE-35) vulnerability in Checkpoint Gaia Os. Its CVSS base score is 5.0 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The Mobile Access Portal's File Share application is vulnerable to a directory traversal attack, allowing an authenticated, malicious end-user (authorized to at least one File Share application) to list the file names of 'nobody'-accessible directories on the Mobile Access gateway.

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.
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-0067Shared CWE-22, CWE-35
CVE-2024-2654Shared CWE-22, CWE-35
CVE-2025-41736Shared CWE-22, CWE-35
CVE-2023-21418Shared CWE-22, CWE-35
CVE-2025-40573Shared CWE-22, CWE-35
CVE-2024-49770Shared CWE-22, CWE-35
CVE-2023-5885Shared CWE-22, CWE-35
CVE-2025-26935Shared CWE-22, CWE-35
CVE-2025-27222Shared CWE-22, CWE-35
CVE-2024-1886Shared CWE-22, CWE-35

Affected Assets

checkpoint
mobile access
all versions
checkpoint
remote access vpn
all versions

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

Mitigating Controls (NIST 800-53 r5) AI

Enforces the intended directory access authorizations that path traversal would otherwise bypass.

Input validation directly neutralizes path sequences so the traversal cannot be introduced or exploited.

Enforces information flow rules that stop unauthorized directory escapes via crafted paths.

Least privilege reduces the impact of any successful traversal by limiting accessible resources.

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 input validation and path sanitization that neutralize traversal sequences.

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 can detect path-traversal flaws before release.

prevents

Secure SDLC mandates input validation and path-handling controls that directly mitigate path traversal.

prevents

Application security requirements include rules for safe file-path construction and canonicalization.

prevents

Secure architecture principles require proper directory restrictions and input sanitization to prevent traversal.

prevents

Secure coding standards explicitly forbid unsafe path concatenation and mandate canonicalization routines.

mitigates

Information access restriction limits file reachability but does not address the input-validation flaw itself.

References