dbcve.org
Amq BrokerApplication · Redhat

CVE-2022-1833

HIGH · 8.8 CVSS v3.1 Published 2022-06-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
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.

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 confidence

The AMQ Broker Operator 7.9.4 deploys with a service account that has excessive clusterwide edit permissions. A low-privilege user with namespace access can discover and exploit these over-privileged secrets to gain cluster-wide edit rights, achieving privilege escalation.

MitigationRestrict the Operator's service account permissions to follow least-privilege principles by removing unnecessary cluster-wide edit permissions and scoping permissions to namespace-level where possible.

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
Amq BrokerApplication
Affected:= 7.9.4

CVSS 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
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm AMQ Broker version
    Run 'kubectl get pods -n <broker-namespace> -o jsonpath="{.items[*].metadata.labels.app\.kubernetes\.version}"' or check the operator deployment version with 'kubectl get deployment -n <broker-namespace>'
    Affected if Version is 7.9.4
  2. Identify the AMQ Broker Operator service account
    Run 'kubectl get serviceaccount -n <broker-namespace>' and look for service accounts with names containing 'artemis', 'broker', or 'amq' in the namespace where the operator is deployed
    Affected if A service account exists in the operator namespace (typically the namespace where AMQ Broker is installed)
  3. Check clusterrole bindings for the operator service account
    Run 'kubectl get clusterrolebindings -o json | jq -r '.items[] | select(.subjects[]? | .kind == "ServiceAccount" and .name == "<sa-name>") | .roleRef.name'' to find clusterrole bindings associated with the operator's service account
    Affected if The service account has one or more clusterrole bindings attached
  4. Verify cluster-wide edit permissions
    Run 'kubectl auth can-i --list --as=system:serviceaccount:<broker-namespace>:<sa-name>' and check if '*' or 'edit' is granted at cluster scope; alternatively run 'kubectl get clusterrolebinding -o json | jq -r '.items[] | select(.roleRef.kind == "ClusterRole" and .roleRef.name == "edit") | .subjects'' to check if the service account is bound to the edit cluster role
    Affected if The service account is bound to a ClusterRole granting edit or broader permissions cluster-wide

You are affected if AMQ Broker 7.9.4 is installed and its operator's service account has cluster-wide edit permissions through clusterrole bindings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict the Operator's service account permissions to follow least-privilege principles by removing unnecessary cluster-wide edit permissions and scoping permissions to namespace-level where possible.

Recommended fix Moderate confidence

Upgrade to AMQ Broker Operator version 7.9.5 or later (check Red Hat security advisory RHSA for exact version)

  1. 1. Identify the AMQ Broker Operator namespace in your cluster
  2. 2. Check the current permissions of the service account used by the AMQ Broker Operator (typically named something like 'amq-broker-operator' or similar)
  3. 3. Review RoleBindings and ClusterRoleBindings associated with the operator's service account
  4. 4. Upgrade the AMQ Broker Operator to a version that includes the security fix for CVE-2022-1833
  5. 5. After upgrade, verify that the operator's service account no longer has excessive cluster-wide permissions
  6. 6. Confirm that the operator still functions correctly with the reduced permission set
Caveat Review release notes for any behavioral changes between 7.9.4 and the fixed version; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Amq Broker Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1833 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-1833 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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