CVE-2022-24721
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCometD 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCometD versions prior to 5.0.11, 6.0.6, and 7.0.6 improperly authorize access to internal Oort and Seti channels, allowing any remote user to subscribe and publish to these cluster-internal communication channels. This enables eavesdropping on sensitive user traffic traversing the cluster and unauthorized modification of user data and cluster state.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 5.0.11>= 6.0.0, < 6.0.6>= 7.0.0, < 7.0.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- 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
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed CometD versionLocate the CometD JAR file or dependency in your project (typically named cometd-*.jar) and check its version. In Maven projects, run 'mvn dependency:tree' or inspect the pom.xml for cometd-version. In runtime, the version is often logged at startup or available via the API.Affected if The installed version is less than 5.0.11, or falls between 6.0.0 and 6.0.5 inclusive, or falls between 7.0.0 and 7.0.5 inclusive.
-
Identify if Oort clustering is enabledSearch your configuration files (XML, JSON, or YAML) for Oort-related configuration. Look for 'oort' bean or channel definitions. Check your startup logs for Oort initialization messages. Inspect your web.xml or application context for Oort servlet or bean configuration.Affected if Oort clustering is enabled and the CometD version is within the affected ranges.
-
Identify if Seti server-to-server communication is enabledSearch configuration files for 'Seti' bean or channel configuration. Look for Seti initialization in your startup logs. Check for Seti-related entries in your CometD channel subscriptions.Affected if Seti is enabled and the CometD version is within the affected ranges.
-
Inspect SecurityPolicy configurationSearch your configuration for a custom SecurityPolicy implementation. Look for classes that extend or implement org.cometd.server.SecurityPolicy. Check if subscription and publishing to channels prefixed with '/oort/' or '/seti/' are explicitly restricted.Affected if No custom SecurityPolicy is defined to block access to '/oort/' and '/seti/' channels, leaving them accessible to any remote user.
You are affected if your CometD version is below 5.0.11, between 6.0.0-6.0.5, or between 7.0.0-7.0.5 AND you have Oort or Seti clustering enabled without a custom SecurityPolicy restricting access to internal channels.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.0.116.0.67.0.6
Upgrade CometD to version 5.0.11, 6.0.6, or 7.0.6, or alternatively implement a custom SecurityPolicy that forbids subscription and publishing to remote non-Oort sessions on Oort and Seti channels.
5.0.11 (for 5.x users), 6.0.6 (for 6.x users), or 7.0.6 (for 7.x users)
- Identify the current CometD version in use by checking project dependencies or build configuration
- Determine which major version line (5.x, 6.x, or 7.x) is currently deployed
- Upgrade to the appropriate fixed version: 5.0.11 for 5.x line, 6.0.6 for 6.x line, or 7.0.6 for 7.x line
- Update the dependency in pom.xml, build.gradle, or equivalent build configuration file
- Rebuild and redeploy the application
- Verify the upgrade by testing that Oort and Seti channels are properly protected and unauthorized subscription/publishing is blocked
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24721 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-24721 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data