CVE-2024-38337: 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

This month

CRITICAL 9.1REMOTEUPGRADE

CVE-2024-38337 is a critical-severity flaw (CVSS 9.1) 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, 6.1.0.0, and 6.2.0.0 could allow an unauthorized attacker to retrieve or alter sensitive information contents due to incorrect permission assignments.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.1 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 58%)
CISA exploited list	No
Weakness	CWE-732
Published	2025-01-19
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

2025-01-19 15:15 UTCPublished CVE record published
2026-06-17 07:39 UTCUpdated Record last modified

ibm sterling secure proxy UPGRADE

Affected: >= 6.0.0.0 and < 6.0.3.1 · 6.1.0.0 · 6.2.0.0

Fixed in: 6.0.3.1

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. UPGRADE to 6.0.3.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade sterling-secure-proxy

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade sterling-secure-proxy

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, 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

3. If no update is available yet, 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-38337?

sterling secure proxy: upgrade to 6.0.3.1. Exact commands for each OS are on this page.

Is CVE-2024-38337 being exploited?

CVE-2024-38337 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-38337 affect?

CVE-2024-38337 affects sterling secure proxy. Severity is critical (CVSS 9.1). 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 attacker to retrieve or alter sensitive information contents due to incorrect permission assignments.

How urgent is CVE-2024-38337?

Priority 47/100. Critical 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-41784 HIGH 7.5 DOWNGRADE 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
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

References

← Back to latest CVEs