Cyber Resilience

CVE-2024-41784

Path Traversal in Ibm Sterling Secure Proxy 6.0.0.0 … 6.1.0

Path Traversal
Published
15 November 2024
Modified
20 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 7.5
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:N/A:N
EPSS Score 0.0064 48th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2024-41784 is a high-severity Triple Dot (CWE-32) vulnerability in Ibm Sterling Secure Proxy. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 48th 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)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

IBM Sterling Secure Proxy 6.0.0.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, and 6.1.0.0 could allow a remote attacker to traverse directories on the system. An attacker could send a specially crafted URL request containing "dot dot dot" sequences (/.../) to view arbitrary files…

more

on the system.

CWE(s)
CWE-32CWE-22

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.
attack.mitre.org →
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.
attack.mitre.org →
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.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-51453Same product: Ibm Sterling Secure Proxy
CVE-2023-35016Same vendor: Ibm
CVE-2023-38012Same vendor: Ibm
CVE-2024-56477Same vendor: Ibm
CVE-2026-2606Same vendor: Ibm
CVE-2023-38019Same vendor: Ibm
CVE-2023-38366Same vendor: Ibm
CVE-2025-3356Same vendor: Ibm
CVE-2023-25689Same vendor: Ibm
CVE-2024-45074Same vendor: Ibm

Affected Assets

ibm
sterling secure proxy
6.0.0.0, 6.0.1.0, 6.0.2.0, 6.0.3.0, 6.1.0

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

AC-3 Access Enforcement good match

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

SI-10 Information Input Validation good match

Input validation directly neutralizes special path elements before pathname construction occurs.

AC-6 Least Privilege partial match

Least privilege reduces the impact of any unauthorized file access obtained via traversal.

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 neutralization that prevent triple-dot traversal.

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.

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

Security testing in development catches path-traversal flaws before release, providing strong but post-coding coverage.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and path-handling rules that directly block triple-dot traversal.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against path traversal and directory-escape attacks.

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

Secure architecture principles reduce exposure to path traversal but do not prescribe the specific coding fix.

A.8.28 Secure coding partial match
prevents

Secure coding standards require canonicalization and filtering of '...' sequences, directly eliminating CWE-32.

A.8.3 Information access restriction partial match
prevents

Information-access-restriction policies limit which files can be reached, mitigating impact but not the traversal vector itself.

References