dbcve.org
Websphere Application ServerApplication · Ibm

CVE-2024-35154

HIGH · 7.2 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to after 9.0.5.20 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 WebSphere Application Server 8.5 and 9.0 could allow a remote authenticated attacker, who has authorized access to the administrative console, to execute arbitrary code. Using specially crafted input, the attacker could exploit this vulnerability to execute arbitrary code on the system. IBM X-Force ID: 292641.

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

Authenticated remote code execution vulnerability in IBM WebSphere Application Server 8.5 and 9.0. An attacker with valid administrative console credentials can inject specially crafted input to execute arbitrary code on the host system.

MitigationApply IBM's security patches for this vulnerability (check IBM Fix Central for applicable APARs). Restrict administrative console access to minimal required users and implement network segmentation to limit exposure.

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
Websphere Application ServerApplication
Affected:>= 8.5.0.0, <= 8.5.5.25>= 9.0.0.0, <= 9.0.5.20

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 WebSphere installation location
    Look for IBM WebSphere Application Server installation directories, typically under /opt/IBM/WebSphere or C:\Program Files\IBM\WebSphere on Windows systems. Check for the AppServer directory structure.
    Affected if WebSphere Application Server is installed on the system
  2. Determine installed version
    Check the version.info file in the AppServer directory, or use the versionInfo.sh (Linux) or versionInfo.bat (Windows) utility located in the bin folder of the WebSphere installation root.
    Affected if The installed version falls within 8.5.0.0 to 8.5.5.25 or 9.0.0.0 to 9.0.5.20
  3. Verify admin console is enabled
    Check the server.xml configuration file for the admin console application (ibm.admin.console) deployment status, typically found in the config/cells directory under the WebSphere profile.
    Affected if The administrative console application is enabled and deployed
  4. Confirm admin console network accessibility
    Review the WC_adminhost and WC_adminhost_secure connector settings in the server.xml or determine if the console port (default 9060/9043) is bound to an external network interface rather than localhost only.
    Affected if The admin console is accessible from network interfaces beyond localhost

The environment is affected if WebSphere Application Server versions 8.5.0.0-8.5.5.25 or 9.0.0.0-9.0.5.20 are installed with the administrative console enabled and network-accessible.

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 9.0.5.20
Interim mitigation

Apply IBM's security patches for this vulnerability (check IBM Fix Central for applicable APARs). Restrict administrative console access to minimal required users and implement network segmentation to limit exposure.

Recommended fix High confidence

Upgrade to WebSphere Application Server 8.5.5.26+ or 9.0.5.21+ (latest available fix pack for your version line)

  1. Identify the current WebSphere Application Server version in use (8.5.x or 9.0.x)
  2. Review the IBM WebSphere Application Server support lifecycle to determine the latest available fix pack for your version line
  3. Download and test the latest fix pack (8.5.5.26 or later for 8.5.x; 9.0.5.21 or later for 9.0.x) in a non-production environment
  4. Apply the fix pack during a scheduled maintenance window
  5. Verify the fix pack installation was successful and the WebSphere Application Server starts without errors
  6. Confirm the vulnerability is resolved by reviewing IBM's security bulletin for this CVE
Caveat Review IBM's fix pack readme for any configuration or migration considerations; test thoroughly in non-production first

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

Fix this in Websphere Application Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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