CVE-2024-41784: 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 tra

This month

HIGH 7.5REMOTEDOWNGRADE

CVE-2024-41784 is a high-severity flaw (CVSS 7.5) affecting sterling secure proxy. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 on the system.

Why this priority

High severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 49%)
CISA exploited list	No
Weakness	CWE-32, CWE-22
Published	2024-11-15
Last modified	2026-06-17

Publisher (CNA): IBM Corporation · Vendor: ibm

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-11-15 16:15 UTCPublished CVE record published
2026-06-17 07:48 UTCUpdated Record last modified

ibm sterling secure proxy DOWNGRADE

Affected: 6.0.0.0 · 6.0.1.0 · 6.0.2.0 · 6.0.3.0 · 6.1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 6.0.0.0

1. Check installed version

apt-cache policy sterling-secure-proxy || rpm -q sterling-secure-proxy || sterling-secure-proxy --version

2. No fixed release: DOWNGRADE to a release before 6.0.0.0 (Debian / Ubuntu)

apt-cache madison sterling-secure-proxy sudo apt install sterling-secure-proxy=<VERSION_BEFORE_6.0.0.0> sudo apt-mark hold sterling-secure-proxy

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list sterling-secure-proxy sudo dnf downgrade sterling-secure-proxy-<VERSION_BEFORE_6.0.0.0> sudo dnf versionlock add sterling-secure-proxy

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-41784?

sterling secure proxy: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-41784 being exploited?

CVE-2024-41784 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-41784 affect?

CVE-2024-41784 affects sterling secure proxy. Severity is high (CVSS 7.5). 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 (/.../)

How urgent is CVE-2024-41784?

Priority 44/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2024-51453 MEDIUM 4.3 UPGRADE IBM Sterling Secure Proxy 6.2.0.0 through 6.2.0.1 could allow a remote attacker to traverse directories on the
CVE-2024-41783 CRITICAL 9.1 UPGRADE IBM Sterling Secure Proxy 6.0.0.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.1.0.0, and 6.2.0.0 could allow a privileged us
CVE-2024-38341 MEDIUM 5.9 UPGRADE IBM Sterling Secure Proxy 6.0.0.0 through 6.0.3.1, 6.1.0.0 through 6.1.0.0, and 6.2.0.0 through 6.2.0.1 uses w
CVE-2024-38337 CRITICAL 9.1 UPGRADE IBM Sterling Secure Proxy 6.0.0.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.1.0.0, and 6.2.0.0 could allow an unauthorized

References

← Back to latest CVEs