dbcve.org
Java SdkApplication · Ibm

CVE-2024-27267

MEDIUM · 5.9 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to after 8.0.8.26 or later.
See remediation →
68/100
Remediation priority · Elevated
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
The Object Request Broker (ORB) in IBM SDK, Java Technology Edition 7.1.0.0 through 7.1.5.18 and 8.0.0.0 through 8.0.8.26 is vulnerable to remote denial of service, caused by a race condition in the management of ORB listener threads.

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

A race condition in the Object Request Broker (ORB) listener thread management in IBM Java SDK versions 7.1.0.0-7.1.5.18 and 8.0.0.0-8.0.8.26 can be exploited remotely to cause denial of service by corrupting the ORB thread pool state.

MitigationUpgrade IBM Java SDK to a version beyond 7.1.5.18 or 8.0.8.26, or apply IBM's subsequent security patch for this vulnerability.

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
Java SdkApplication
Affected:>= 7.1.0.0, <= 7.1.5.18>= 8.0.0.0, <= 8.0.8.26

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

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 Java SDK installation and version
    Run 'java -version' from the command line or inspect the java.version system property via 'java -XshowSettings:properties -version'. Look for 'IBM' or 'J9' in the output to confirm IBM Java SDK.
    Affected if The reported version falls within 7.1.0.0 through 7.1.5.18, or within 8.0.0.0 through 8.0.8.26.
  2. Confirm the specific IBM Java SDK release line
    Examine the full version string from the previous step. IBM Java SDK 7.x and 8.x have distinct release cycles.
    Affected if The version indicates IBM Java SDK 7.1.0.0 through 7.1.5.18, or version 8.0.0.0 through 8.0.8.26.
  3. Determine if the ORB feature is in use
    Review application configuration files for CORBA ORB initialization (for example, orb.properties, or code using org.omg.CORBA.ORB). Check running processes or deployment manifests for ORB-related Java classes or -Dorg.omg.CORBA.ORBClass arguments.
    Affected if The IBM Java SDK version is within the affected range AND the application utilizes the CORBA Object Request Broker functionality.

You are affected if you are running IBM Java SDK versions 7.1.0.0-7.1.5.18 or 8.0.0.0-8.0.8.26 and your application uses the CORBA ORB feature.

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 a release after 8.0.8.26
Interim mitigation

Upgrade IBM Java SDK to a version beyond 7.1.5.18 or 8.0.8.26, or apply IBM's subsequent security patch for this vulnerability.

Recommended fix High confidence

IBM SDK Java Technology Edition 7.1.5.19 (or latest 7.1.x) / 8.0.8.27 (or latest 8.0.x)

  1. 1. Identify the current IBM Java SDK version in use by running 'java -version' or checking the installation directory
  2. 2. Download the latest IBM Java SDK 7.1.x or 8.0.x version from IBM's official website or fix central
  3. 3. Install the new version following IBM's standard installation procedures
  4. 4. Update JAVA_HOME environment variable to point to the new installation path
  5. 5. Verify the installation by running 'java -version' to confirm the new version is active
  6. 6. Test critical applications to ensure compatibility with the new Java version
  7. 7. Update any build scripts, container images, or deployment configurations that reference the old Java path
Caveat Review IBM Java 7.1.6+ and 8.0.9+ release notes for any compatibility changes; minor version upgrades typically have low risk

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

Fix this in Java Sdk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-27267 — 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-27267 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