CVE-2024-27268 json
IBM WebSphere Application Server Liberty denial of service
published 2024-04-04 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-24507
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
IBM WebSphere Application Server Liberty 18.0.0.2 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: 284574.
Patch / fix
- ibm websphere_application_server 24.0.0.5
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-27268 updated
ibm-WebSphere: CONTINUATION frames DoS
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
1.28% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- IBM WebSphere Application Server Liberty
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
ibm.com
/support/pages/node/7145809
vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/284574
vdb-entry, vendor-advisory
-
kb.cert.org
/vuls/id/421644
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2024-27268
- NVD CVE-2024-27268
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.