Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-39747: IBM Sterling Connect:Direct Web Services 6.0, 6.1, 6.2, and 6.3 uses default credentials for potentially criti

47
This month
HIGH 8.1REMOTEUPGRADE

CVE-2024-39747 is a high-severity flaw (CVSS 8.1) affecting sterling connect direct web services. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

IBM Sterling Connect:Direct Web Services 6.0, 6.1, 6.2, and 6.3 uses default credentials for potentially critical functionality.

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score8.1 (High)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance0.8% (top 45%)
CISA exploited listNo
WeaknessCWE-1392
Published2024-08-31
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 connect direct web services UPGRADE
Affected: >= 6.0.0.0 and < 6.1.0.25 · >= 6.2.0 and < 6.2.0.24 · >= 6.3.0 and < 6.3.0.9
Fixed in: 6.1.0.25, 6.2.0.24, 6.3.0.9
Safe to downgrade to: a release before 6.0.0.0
1. Check installed version
apt-cache policy sterling-connect-direct-web-services || rpm -q sterling-connect-direct-web-services || sterling-connect-direct-web-services --version
2. UPGRADE to 6.1.0.25 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade sterling-connect-direct-web-services
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade sterling-connect-direct-web-services
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-connect-direct-web-services sudo apt install sterling-connect-direct-web-services=<VERSION_BEFORE_6.0.0.0> sudo apt-mark hold sterling-connect-direct-web-services
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list sterling-connect-direct-web-services sudo dnf downgrade sterling-connect-direct-web-services-<VERSION_BEFORE_6.0.0.0> sudo dnf versionlock add sterling-connect-direct-web-services
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-39747?

sterling connect direct web services: upgrade to 6.1.0.25, 6.2.0.24, 6.3.0.9. Exact commands for each OS are on this page.

Is CVE-2024-39747 being exploited?

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

CVE-2024-39747 affects sterling connect direct web services. Severity is high (CVSS 8.1). IBM Sterling Connect:Direct Web Services 6.0, 6.1, 6.2, and 6.3 uses default credentials for potentially critical functionality.

How urgent is CVE-2024-39747?

Priority 47/100. High severity; 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.