CVE-2022-24721
HIGHCVE-2022-24721 is a high-severity (CVSS 8.1) CWE-863 vulnerability in org.cometd.java:cometd-java-oort. O3 Security confirms whether CVE-2022-24721 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Incorrect Authorization in org.cometd.oort
Real-World Exposure
org.cometd.java:cometd-java-oort☕org.cometd.java:cometd-java-oort☕org.cometd.java:cometd-java-oortReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
CometD is a scalable comet implementation for web messaging. In any version prior to 5.0.11, 6.0.6, and 7.0.6, internal usage of Oort and Seti channels is improperly authorized, so any remote user could subscribe and publish to those channels. By subscribing to those channels, a remote user may be able to watch cluster-internal traffic that contains other users' (possibly sensitive) data. By publishing to those channels, a remote user may be able to create/modify/delete other user's data and modify the cluster structure. A fix is available in versions 5.0.11, 6.0.6, and 7.0.6. As a workaround, install a custom SecurityPolicy that forbids subscription and publishing to remote, non-Oort, sessions on Oort and Seti channels.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.cometd.java:cometd-java-oort | all versions | 5.0.11 |
| ☕Maven | org.cometd.java:cometd-java-oort | ≥ 6.0.0&&< 6.0.6 | 6.0.6 |
| ☕Maven | org.cometd.java:cometd-java-oort | ≥ 7.0.0&&< 7.0.6 | 7.0.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.cometd.java:cometd-java-oort. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.cometd.java:cometd-java-oort to 5.0.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24721 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2022-24721 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2022-24721. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-24721 in your dependencies?
O3 detects CVE-2022-24721 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.