# CVE-2022-1833: Privilege escalation in AMQ Broker Operator

> A low-privilege user can gain cluster-wide edit rights by exploiting excessive permissions in the AMQ Broker Operator service account.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-fmxp-97xc-fcmx

## What is CVE-2022-1833?

CVE-2022-1833 is a high-severity vulnerability in AMQ Broker Operator, published on 21 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2022-1833?

It affects 1 product.


Products: Redhat Amq Broker.

## How do I fix CVE-2022-1833?

No fix has been published for CVE-2022-1833 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-1833 being exploited?

There is no known exploitation of CVE-2022-1833 in the wild and no public exploit code.

## Other vulnerabilities in AMQ Broker Operator

- [CVE-2021-3763](https://insights.sbomify.com/CVE-2021-3763/): Missing authorization in AMQ Broker (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1833 and fix it if it is affected.

What it is: CVE-2022-1833 is a high-severity vulnerability in AMQ Broker Operator, published on 21 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1833 in the wild and no public exploit code.

Affected product: AMQ Broker Operator. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-1833/ (Markdown: https://insights.sbomify.com/CVE-2022-1833/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1833
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1833
- OSV: https://osv.dev/vulnerability/CVE-2022-1833

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-1833/
Summaries are generated and may contain mistakes; the official description above is the record.