Improper Authorization in org.cometd.oort

高 8.1CVE-2022-24721 · GHSA-rjmq-6v55-4rjv · 15/03/2022 公開 · 17/06/2026 更新

要点

CVE-2022-24721 は org.cometd.java:cometd-java-oort, cometd (cometd) に影響する深刻度「高」 (CVSS 8.1) の脆弱性です。
今後30日間に悪用される確率（EPSS）：1.1%（全脆弱性の 67.0% より高い）。
対処：6.0.6, 7.0.6, 5.0.11 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
org.cometd.java:cometd-java-oort Maven	`≥ 6.0.0, < 6.0.6≥ 7.0.0, < 7.0.6< 5.0.11`	`6.0.67.0.65.0.11`
cometd cometd	`≥ 6.0.0, < 6.0.6≥ 7.0.0, < 7.0.6< 5.0.11`	`6.0.67.0.65.0.11`

概要

Impact

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 user's (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. The issue impacts any version up to 5.0.10, 6.0.5 and 7.0.5.

Patches

The issue has been fixed in 5.0.11, 6.0.6 and 7.0.6.

Workarounds

The workaround is to install a custom SecurityPolicy that forbids subscription and publishing to remote, non-Oort, sessions on Oort and Seti channels. This workaround could be implemented in any affected version.

References

cometd/cometd#1146

For more information

If you have any questions or comments about this advisory:

Email us at [email protected]

Credits

https://www.redteam-pentesting.de/

NVD の説明

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.