CVE-2022-1833
First published: Mon May 23 2022(Updated: )
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.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Redhat Amq Broker | =7.9.4 |
Remedy
In order to have these privileges correctly set in this version, opt for using the CLI method at https://access.redhat.com/documentation/en-us/red_hat_amq/7.4/html/deploying_amq_broker_on_openshift_container_platform/broker-operator-broker-ocp#operator-install-broker-ocp Make sure to use the latest available version in order to have access to the latest bug and security fixes.
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://bugzilla.redhat.com/show_bug.cgi?id=2089406#c4
- https://access.redhat.com/errata/RHSA-2022:5101
- https://access.redhat.com/security/cve/cve-2022-1833
- https://bugzilla.redhat.com/show_bug.cgi?id=2089406
- https://www.cve.org/CVERecord?id=CVE-2022-1833 https://nvd.nist.gov/vuln/detail/CVE-2022-1833 https://access.redhat.com/documentation/en-us/red_hat_amq/7.4/html/deploying_amq_broker_on_openshift_container_platform/broker-operator-broker-ocp
Frequently Asked Questions
What is the severity of CVE-2022-1833?
The severity of CVE-2022-1833 is high with a severity value of 8.8.
How does CVE-2022-1833 affect AMQ Broker Operator?
CVE-2022-1833 affects AMQ Broker Operator 7.9.4.
How can a low-privilege user exploit CVE-2022-1833?
A low-privilege user with access to the namespace where AMQ Operator is deployed can exploit CVE-2022-1833 by checking the secrets to gain clusterwide edit rights.
What is the solution for CVE-2022-1833?
To mitigate CVE-2022-1833, apply the patch or upgrade to a version of AMQ Broker Operator that is not affected.
Where can I find more information about CVE-2022-1833?
You can find more information about CVE-2022-1833 in the CVE record, NVD, Red Hat documentation, and relevant bugzilla and errata pages.
- collector/redhat-cve
- collector/nvd-index
- agent/type
- agent/softwarecombine
- agent/first-publish-date
- agent/last-modified-date
- agent/tags
- agent/author
- agent/references
- agent/severity
- agent/remedy
- agent/weakness
- agent/description
- agent/event
- collector/mitre-cve
- source/MITRE
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2022-1833
- vendor/redhat
- canonical/redhat amq broker
- version/redhat amq broker/7.9.4