CVE-2024-39745
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM Sterling Connect:Direct Web Services 6.0, 6.1, 6.2, and 6.3 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIBM Sterling Connect:Direct Web Services versions 6.0 through 6.3 implement weak cryptographic algorithms that could enable an attacker to decrypt sensitive data transmitted or stored through the system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 6.0= 6.1.0= 6.2.0= 6.3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of IBM Sterling Connect:Direct Web ServicesLocate the product's version information through the application binaries, installation directory, or administration consoleAffected if The installed version is 6.0, 6.1.0, 6.2.0, or 6.3.0
-
Locate SSL/TLS configuration filesFind the configuration files that control SSL/TLS settings for the web services component, typically in the installation directory or config folderAffected if The configuration files exist and can be examined for cryptographic settings
-
Inspect enabled SSL/TLS protocolsReview the configuration to determine which protocols are enabled (e.g., SSLv3, TLS 1.0, TLS 1.1)Affected if Legacy or deprecated protocols such as SSLv3, TLS 1.0, or TLS 1.1 are enabled
-
Review cipher suite configurationExamine the cipher suites defined in the configuration for weak or deprecated algorithms (e.g., NULL, EXPORT, RC4, 3DES, MD5-based suites)Affected if Weak or deprecated cipher suites are enabled or configured
A user is affected if IBM Sterling Connect:Direct Web Services version 6.0, 6.1.0, 6.2.0, or 6.3.0 is installed and the SSL/TLS configuration supports weak cryptographic algorithms or deprecated protocols.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of IBM Sterling Connect:Direct Web Services that implements stronger cryptographic algorithms, or reconfigure the application to use strong cipher suites and protocols (e.g., TLS 1.2+ with AES-256).
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39745 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-39745 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data