dbcve.org
Websphere Application ServerApplication · Ibm

CVE-2024-27270

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 24.0.0.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Liberty 23.0.0.3 through 24.0.0.3 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in a specially crafted URI. IBM X-Force ID: 284576.

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 WebSphere Application Server Liberty versions 23.0.0.3 through 24.0.0.3 contains a cross-site scripting (XSS) vulnerability that allows attackers to inject arbitrary JavaScript code through specially crafted URIs. This occurs due to insufficient input validation in the web interface, enabling authenticated or tricked users to execute malicious scripts in the context of other users' sessions.

MitigationUpgrade IBM WebSphere Application Server Liberty to a version beyond 24.0.0.3 or apply the appropriate IBM security patch. Additionally, implement output encoding and input validation as defense-in-depth measures.

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:>= 23.0.0.3, < 24.0.0.4

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 installed WebSphere Liberty version
    Check the version.properties file in the wlp/lib/versions directory, or run 'java -jar wlp/tools/wlp-product-info.jar' from the installation root, or view the version in the admin console under 'Runtime' > 'Information'.
    Affected if The installed version is 23.0.0.3, 23.0.0.4, 23.0.0.5, 23.0.0.6, 23.0.0.7, 23.0.0.8, 23.0.0.9, 23.0.0.10, 23.0.0.11, 23.0.0.12, or any 24.0.0.x version prior to 24.0.0.4.
  2. Verify if the admin console or web interface is enabled
    Check the server.xml configuration file for the 'adminCenter-1.0' feature or other web-based admin features being enabled. Look for <feature>adminCenter-1.0</feature> or similar entries.
    Affected if The adminCenter-1.0 feature or any web-based administrative interface feature is enabled in server.xml.
  3. Confirm web interface is network accessible
    Attempt to access the admin console URL (typically https://localhost:9443/adminCenter or /ibm/console) or check the httpEndpoint configuration in server.xml to verify the listener is active and bound to a network interface.
    Affected if The administrative web interface is accessible over the network (not bound to localhost only).
  4. Review HTTP access logs for suspicious URI patterns
    Examine HTTP access logs in the logs/http_access.log file for URIs containing script tags, javascript:, or other XSS payloads in query parameters.
    Affected if Unusual or malicious URI patterns containing script injection attempts are present in the access logs.

You are affected if the installed WebSphere Liberty version is between 23.0.0.3 and 24.0.0.3 inclusive and the administrative web interface is enabled and 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 24.0.0.4 or later
Fixed in 24.0.0.4
Interim mitigation

Upgrade IBM WebSphere Application Server Liberty to a version beyond 24.0.0.3 or apply the appropriate IBM security patch. Additionally, implement output encoding and input validation as defense-in-depth measures.

Recommended fix High confidence

24.0.0.4 or later

  1. Back up the current WebSphere Application Server Liberty installation and all configurations
  2. Download IBM WebSphere Application Server Liberty version 24.0.0.4 or later from IBM Fix Central (https://www.ibm.com/support/fixcentral/)
  3. Install the updated version following IBM's installation documentation
  4. Verify the installation was successful by checking the version number
  5. Test that applications function correctly with the updated version
  6. Consult IBM's migration/upgrade documentation if needed for any additional post-upgrade steps
Caveat Minor version upgrade within same release line; review IBM release notes for any behavior changes

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

Fix this in Websphere Application Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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