CometD has acknowledgement extension out of memory
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.0.23, 6.0.19, 7.0.19, 8.0.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
CometD is a scalable comet implementation for web messaging. In versions 5.0.0 through 5.0.22, 6.0.0 through 6.0.18, 7.0.0 through 7.0.18, and 8.0.0 through 8.0.8, bad clients that always send a fixed batch value when the server is using the acknowledgement extension may cause the unacknowledged message queue to grow indefinitely, eventually causing an `OutOfMemoryError`. Versions 5.0.23, 6.0.19, 7.0.19, and 8.0.9 patch the issue. As a workaround, disable the acknowledgement extension.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- cometd cometd
From 5.0.0 · fixed in 5.0.23; From 6.0.0 · fixed in 6.0.19; From 7.0.0 · fixed in 7.0.19; From 8.0.0 · fixed in 8.0.9
- org.cometd.java:cometd-java-server-commonMaven
From 5.0.0 · fixed in 5.0.23
- org.cometd.java:cometd-java-server-commonMaven
From 6.0.0 · fixed in 6.0.19
- org.cometd.java:cometd-java-server-commonMaven
From 7.0.0 · fixed in 7.0.19
- org.cometd.java:cometd-java-server-commonMaven
From 8.0.0 · fixed in 8.0.9