dbcve.org
Websphere Application ServerApplication · Ibm

CVE-2024-22353

HIGH · 7.5 CVSS v3.1 Published 2024-03-31
Fix available
A fix is available. Upgrade to after 24.0.0.3 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 WebSphere Application Server Liberty 17.0.0.3 through 24.0.0.4 is vulnerable to a denial of service, caused by sending a specially crafted request. A remote attacker could exploit this vulnerability to cause the server to consume memory resources. IBM X-Force ID: 280400.

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 confidence

IBM WebSphere Application Server Liberty versions 17.0.0.3 through 24.0.0.4 contains a denial of service vulnerability where a specially crafted HTTP request causes excessive memory consumption on the server, potentially leading to resource exhaustion and service unavailability.

MitigationApply the IBM fix/patch for this vulnerability (refer to IBM X-Force ID 280400 for official remediation). As a temporary mitigation, consider implementing request size limits, rate limiting, or web application firewall rules to block abnormally large or suspicious requests.

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:>= 17.0.0.3, <= 24.0.0.3

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/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 the installed WebSphere Liberty version
    Run the command 'server version' from the Liberty installation bin directory, or check the version string in the installation manifest or productInfo.xml file located in the lib/versions directory.
    Affected if The version number falls within 17.0.0.3 through 24.0.0.3 (or 24.0.0.4 depending on official advisory scope).
  2. Confirm the product is WebSphere Application Server Liberty
    Verify the product name from the server version output or installation files shows 'WebSphere Application Server Liberty' or 'IBM WebSphere Liberty'.
    Affected if The product is IBM WebSphere Application Server Liberty running an affected version.
  3. Determine if HTTP connectors are enabled
    Check the server.xml configuration file for enabled httpEndpoint elements or HTTP transport channels. Look for <httpEndpoint> definitions with enabled='true' or default settings.
    Affected if HTTP endpoints are exposed and accepting requests, as the vulnerability is triggered via specially crafted HTTP requests.
  4. Check for external network exposure
    Review network configuration to determine if the Liberty HTTP ports (default 9080, 9443, or custom ports) are accessible from untrusted networks or the public internet.
    Affected if The HTTP ports are externally accessible, increasing the likelihood of exploitation.

You are affected if you are running IBM WebSphere Application Server Liberty version 17.0.0.3 through 24.0.0.3 with HTTP endpoints enabled and exposed to network traffic that could contain specially crafted requests.

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

Apply the IBM fix/patch for this vulnerability (refer to IBM X-Force ID 280400 for official remediation). As a temporary mitigation, consider implementing request size limits, rate limiting, or web application firewall rules to block abnormally large or suspicious requests.

Recommended fix High confidence

IBM WebSphere Application Server Liberty 24.0.0.4 or later fix pack

  1. 1. Identify the current IBM WebSphere Application Server Liberty version by checking the product installation or server logs
  2. 2. Obtain the latest IBM WebSphere Application Server Liberty fix pack or interim fix (iFix) that addresses CVE-2024-22353
  3. 3. Download the fix from IBM Fix Central (https://www.ibm.com/support/fixcentral/) or through IBM entitlement
  4. 4. Apply the fix following IBM's standard installation instructions for your deployment model (traditional or container)
  5. 5. Restart the WebSphere Liberty server to ensure the fix takes effect
  6. 6. Verify the server starts successfully and monitor for normal memory usage
Caveat Standard fix pack upgrade should not introduce breaking changes; always review IBM's fix pack release notes before applying in production

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
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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