dbcve.org
Semeru RuntimeApplication · Ibm

CVE-2024-22361

HIGH · 7.5 CVSS v3.1 Published 2024-02-10
Fix available
A fix is available. Upgrade to 8.0.402.0 / 11.0.22.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
IBM Semeru Runtime 8.0.302.0 through 8.0.392.0, 11.0.12.0 through 11.0.21.0, 17.0.1.0 - 17.0.9.0, and 21.0.1.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 281222.

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 · high confidence

IBM Semeru Runtime versions 8.0.302.0 through 8.0.392.0, 11.0.12.0 through 11.0.21.0, 17.0.1.0 through 17.0.9.0, and 21.0.1.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.

MitigationUpgrade IBM Semeru Runtime to a patched version beyond 8.0.392.0, 11.0.21.0, 17.0.9.0, and 21.0.1.0 that addresses the weak cryptographic algorithms. Review and enforce stronger cryptographic configurations (e.g., disable weak ciphers, use TLS 1.2+) in application configurations.

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
Semeru RuntimeApplication
Affected:>= 8.0.302.0, < 8.0.402.0>= 11.0.12.0, < 11.0.22.0>= 17.0.1.0, < 17.0.10.0= 21.0.1.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify IBM Semeru Runtime installation
    Run 'java -version' or 'java -XshowSettings:properties -version' to display the JRE/JDK vendor and version information. Look for 'IBM Semeru Runtime' in the output.
    Affected if The output shows IBM Semeru Runtime as the installed JRE/JDK
  2. Determine the installed Semeru version
    Locate the full version string from the 'java -version' output (for example: 8.0.302.0, 11.0.20.0, 17.0.8.0, or 21.0.1.0). Note that the version format may appear as 8.0.30.2, 11.0.12.0, etc. in some outputs.
    Affected if The installed version falls within: 8.0.302.0 through 8.0.392.0, 11.0.12.0 through 11.0.21.0, 17.0.1.0 through 17.0.9.0, or exactly 21.0.1.0
  3. Verify weak cryptographic configuration usage
    Review application configuration files (such as javax.net.ssl properties, SSLContext settings, or custom cipher suite configurations) for any explicit use of weak algorithms or fallback to default Java security settings.
    Affected if The application relies on default cryptographic settings or explicitly configures weak cipher suites vulnerable to the weaker algorithms present in affected Semeru versions

You are affected if IBM Semeru Runtime is installed and its version matches one of the vulnerable ranges (8.0.302.0 to 8.0.392.0, 11.0.12.0 to 11.0.21.0, 17.0.1.0 to 17.0.9.0, or exactly 21.0.1.0) while using cryptography to protect sensitive data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 8.0.402.0 / 11.0.22.0 / 17.0.10.0 or later
Fixed in 8.0.402.011.0.22.017.0.10.0
Interim mitigation

Upgrade IBM Semeru Runtime to a patched version beyond 8.0.392.0, 11.0.21.0, 17.0.9.0, and 21.0.1.0 that addresses the weak cryptographic algorithms. Review and enforce stronger cryptographic configurations (e.g., disable weak ciphers, use TLS 1.2+) in application configurations.

Recommended fix High confidence

Semeru Runtime 8.0.402.0+ (Java 8), 11.0.22.0+ (Java 11), 17.0.10.0+ (Java 17), or 21.0.2.0+ (Java 21)

  1. 1. Identify the current IBM Semeru Runtime version in use by checking the java.version system property
  2. 2. For Java 8 (Semeru 8.x): upgrade to Semeru Runtime version 8.0.402.0 or later
  3. 3. For Java 11 (Semeru 11.x): upgrade to Semeru Runtime version 11.0.22.0 or later
  4. 4. For Java 17 (Semeru 17.x): upgrade to Semeru Runtime version 17.0.10.0 or later
  5. 5. For Java 21 (Semeru 21.x): upgrade to a version newer than 21.0.1.0 (e.g., 21.0.2.0 or later when available)
  6. 6. Download the appropriate Semeru Runtime version from IBM's official website or trusted distribution channels
  7. 7. Test the application thoroughly with the new runtime to ensure compatibility
  8. 8. Deploy the upgraded runtime to production environments
Caveat Standard Java upgrade considerations apply - review release notes for any behavioral changes and ensure application compatibility testing is performed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Semeru Runtime Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22361 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22361 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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