Skip to content
Fencer Intel
high 8.1

CVE-2022-24721 json

Incorrect Authorization in org.cometd.oort

published 4y ago modified 4mo ago also GHSA-rjmq-6v55-4rjv , EUVD-2022-1534

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.cometd.java:cometd-java-oort 5.0.11, 6.0.6, 7.0.6
  • cometd cometd 5.0.11, 6.0.6, 7.0.6

Is CVE-2022-24721 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2022-24721 updated cvss 8.1

cometd: Improper Authorization in org.cometd.oort

  • Red Hat Integration Data Virtualisation Operator cometd cometd Red Hat JBoss Fuse 6 cometd cometd Red Hat JBoss Fuse Service Works 6 cometd cometd
    affected: no fix planned “Out of support scope”
  • Red Hat build of Quarkus cometd cometd Red Hat Fuse 7 cometd cometd Red Hat Integration Camel K 1 cometd cometd Red Hat Integration Camel Quarkus 1 cometd cometd
    not 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
total
Assessed
last yr.

Exploit prediction

1.15% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 5.5 AV:N/AC:L/Au:S/C:P/I:P/A:N
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected 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.11
6.0.6
7.0.6

Affected products

  • cometd cometd

Classification

Weakness

References

Sources

Fencer Intel 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.