CVE-2022-24721
cometd: Improper Authorization in org.cometd.oort
Overview
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.
Source: OX vulnerability database
Severity
8.1 · HIGH
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Weakness: CWE-863
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Maven | org.cometd.java:cometd-java-oort | <5.0.11>=6.0.0, <6.0.6>=7.0.0, <7.0.6 | 5.0.116.0.67.0.6 |
Open a package to see all its vulnerabilities.
Operating systems
No Linux distribution reports this ID.
References
- access.redhat.com https://access.redhat.com/security/cve/CVE-2022-24721
- github.com https://github.com/cometd/cometd
- github.com https://github.com/cometd/cometd/commit/bb445a143fbf320f17c62e340455cd74acfb5929
- github.com https://github.com/cometd/cometd/issues/1146
- github.com https://github.com/cometd/cometd/security/advisories/GHSA-rjmq-6v55-4rjv
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2022-24721
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2022-24721
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.