CyberSecBulletin
CVE-2022-1833NVD status: Modified

AMQ Broker Operator: Incorrect Default Permissions

CVE-2022-1833 is a high-severity incorrect default permissions vulnerability in AMQ Broker Operator, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected AMQ Broker Operator versions: AMQ Broker Operator 7.9.4 and prior. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.88% chance of exploitation within 30 days, higher than 60% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of AMQ Broker Operator you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on bugzilla.redhat.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
AMQ Broker OperatorAMQ Broker OperatorAMQ Broker Operator 7.9.4 and priorNot stated
Red HatAmq Broker7.9.4Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.8HighNVD
CVSS 2.06.5MediumNVD

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Incorrect Default Permissions

During installation, installed file permissions are set to allow anyone to modify those files.

How developers prevent this class of flaw

  • The architecture needs to access and modification attributes for files to only those users who actually require those actions.
  • Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

More Incorrect Default Permissions vulnerabilities (CWE-276)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Recent Incorrect Default Permissions vulnerabilities

Spotted an error? Tell us.