Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

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

29
Routine
MEDIUM 5.9REMOTEUPGRADE

CVE-2024-38341 is a medium-severity flaw (CVSS 5.9) 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 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 weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.

Why this priority

  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score5.9 (Medium)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance0.2% (top 86%)
CISA exploited listNo
WeaknessCWE-328, CWE-326
Published2025-05-28
Last modified2026-06-17
Publisher (CNA): IBM Corporation · Vendor: ibm

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

ibm sterling secure proxy UPGRADE
Affected: >= 6.0.0.0 and <= 6.0.3.1 · >= 6.1.0.0 and <= 6.1.0.1 · >= 6.2.0.0 and <= 6.2.0.1
Fixed in: newer than 6.2.0.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 newer than 6.2.0.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-38341?

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

Is CVE-2024-38341 being exploited?

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

CVE-2024-38341 affects sterling secure proxy. Severity is medium (CVSS 5.9). 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 weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.

How urgent is CVE-2024-38341?

Priority 29/100. Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.