| Package | Affected versions | Patched versions |
|---|---|---|
| org.cometd.java:cometd-java-oort | ≥ 6.0.0, < 6.0.6≥ 7.0.0, < 7.0.6< 5.0.11 | 6.0.67.0.65.0.11 |
| cometd | ≥ 6.0.0, < 6.0.6≥ 7.0.0, < 7.0.6< 5.0.11 | 6.0.67.0.65.0.11 |
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.
The issue has been fixed in 5.0.11, 6.0.6 and 7.0.6.
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.
cometd/cometd#1146
If you have any questions or comments about this advisory:
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free