GHSA-RJMQ-6V55-4RJV

Vulnerability from github – Published: 2022-03-15 19:02 – Updated: 2022-03-15 19:02
VLAI?
Summary
Improper Authorization in org.cometd.oort
Details

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 security@webtide.com

Credits

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

Severity ?
8.1 (High)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.cometd.java:cometd-java-oort"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.0.11"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.cometd.java:cometd-java-oort"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "6.0.0"
            },
            {
              "fixed": "6.0.6"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.cometd.java:cometd-java-oort"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "7.0.0"
            },
            {
              "fixed": "7.0.6"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2022-24721"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-863"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2022-03-15T19:02:36Z",
    "nvd_published_at": "2022-03-15T14:15:00Z",
    "severity": "HIGH"
  },
  "details": "### Impact\nInternal usage of Oort and Seti channels is improperly authorized, so any remote user could subscribe and publish to those channels.\nBy subscribing to those channels, a remote user may be able to watch cluster-internal traffic that contains other user\u0027s (possibly sensitive) data.\nBy publishing to those channels, a remote user may be able to create/modify/delete other user\u0027s data and modify the cluster structure.\nThe issue impacts any version up to 5.0.10, 6.0.5 and 7.0.5.\n\n### Patches\nThe issue has been fixed in 5.0.11, 6.0.6 and 7.0.6.\n\n### Workarounds\nThe workaround is to install a custom `SecurityPolicy` that forbids subscription and publishing to remote, non-Oort, sessions on Oort and Seti channels.\nThis workaround could be implemented in any affected version.\n\n### References\ncometd/cometd#1146\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [security@webtide.com](mailto:security@webtide.com)\n\n### Credits\nhttps://www.redteam-pentesting.de/",
  "id": "GHSA-rjmq-6v55-4rjv",
  "modified": "2022-03-15T19:02:36Z",
  "published": "2022-03-15T19:02:36Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/cometd/cometd/security/advisories/GHSA-rjmq-6v55-4rjv"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-24721"
    },
    {
      "type": "WEB",
      "url": "https://github.com/cometd/cometd/issues/1146"
    },
    {
      "type": "WEB",
      "url": "https://github.com/cometd/cometd/commit/bb445a143fbf320f17c62e340455cd74acfb5929"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/cometd/cometd"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Improper Authorization in org.cometd.oort"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.