CVE-2022-24721: Improper Authorization in org.cometd.oort

Summary

15/03/2022
Yes i
High
8.1

CVE-2022-24721: Improper Authorization in org.cometd.oort. Affects org.cometd.java:cometd-java-oort across 3 version ranges.

< 5.0.11 >= 6.0.0, < 6.0.6 >= 7.0.0, < 7.0.6

Fixed in 5.0.11, 6.0.6 or 7.0.6, depending on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The org.cometd.java:cometd-java-oort package is a component of the CometD project, which is an open-source implementation of the Bayeux protocol. The package provides functionality for clustering CometD servers using the Oort and Seti channels. These channels allow communication between different instances of CometD servers in a cluster. However, prior to version 5.0.11, 6.0.6, and 7.0.6, the package had an improper authorization vulnerability that allowed remote users to subscribe and publish to the Oort and Seti channels without proper authentication. This vulnerability could lead to unauthorized access to sensitive data, modification of data, and manipulation of the cluster structure.

Vulnerability Detail

The vulnerability in org.cometd.oort allows remote users to subscribe and publish to the Oort and Seti channels without proper authorization. This means that any remote user can access and manipulate cluster-internal traffic, potentially exposing sensitive data. By subscribing to these channels, an attacker can monitor the communication between different instances of CometD servers in the cluster, gaining access to potentially sensitive information. Additionally, by publishing to these channels, an attacker can modify or delete data belonging to other users and manipulate the structure of the cluster. The vulnerability affects versions up to 5.0.10, 6.0.5, and 7.0.5 of the package.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 5.0.11 5.0.11
  • >= 6.0.0, < 6.0.6 6.0.6
  • >= 7.0.0, < 7.0.6 7.0.6

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

If updating the package is not immediately feasible, a workaround can be implemented by installing a custom SecurityPolicy that forbids subscription and publishing to remote, non-Oort, sessions on the Oort and Seti channels. This workaround can be applied to any affected version of the package. The custom SecurityPolicy should be configured to only allow authorized users to subscribe and publish to the Oort and Seti channels, ensuring that only trusted entities can access and manipulate the cluster-internal traffic.

Conclusion

The org.cometd.java:cometd-java-oort package prior to version 5.0.11, 6.0.6, and 7.0.6 is vulnerable to improper authorization, allowing remote users to subscribe and publish to the Oort and Seti channels without proper authentication. This can result in unauthorized access to sensitive data, data modification, and manipulation of the cluster structure. It is recommended to update the package to the fixed versions or apply the provided workaround. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for org.cometd.java:cometd-java-oort →

Share this vulnerability

FAQ

The vulnerability allows remote users to subscribe and publish to the Oort and Seti channels without proper authorization. This can lead to unauthorized access to sensitive data, modification of data, and manipulation of the cluster structure.

Versions up to 5.0.10, 6.0.5, and 7.0.5 of the org.cometd.java:cometd-java-oort package are affected by this vulnerability.

To fix the vulnerability, update the package to version 5.0.11, 6.0.6, or 7.0.6, where the issue has been resolved.

Yes, a workaround is available by installing a custom SecurityPolicy that restricts subscription and publishing to authorized users on the Oort and Seti channels.

More information about this vulnerability can be found in the CometD project's GitHub repository: cometd/cometd#1146

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 5.0.11 5.0.11
  • >= 6.0.0, < 6.0.6 6.0.6
  • >= 7.0.0, < 7.0.6 7.0.6

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback