Apache ActiveMQ Artemis: Improper Authorization
CVE-2023-50780 is a high-severity improper authorization vulnerability in Apache ActiveMQ Artemis from Apache, 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. The record lists version 2.29.0 as the first without the flaw, so updating Apache ActiveMQ Artemis to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 17.3% chance of exploitation within 30 days, which is in the top 2.84% of all scored CVEs.
EPSS places it among the vulnerabilities most likely to be exploited soon.
What to do
- Update Apache ActiveMQ Artemis to 2.29.0 or a later version.
- Update Artemis to 2.29.0 or a later version.
- Read the advisory on lists.apache.org for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Apache | Apache ActiveMQ Artemis | before 2.29.0 | 2.29.0 |
| Apache | Artemis | before 2.29.0 | 2.29.0 |
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 system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | NVD |
| CVSS 3.1 | 8.8 | High | CISA (ADP) |
Official description
Apache ActiveMQ Artemis allows access to diagnostic information and controls through MBeans, which are also exposed through the authenticated Jolokia endpoint. Before version 2.29.0, this also included the Log4J2 MBean. This MBean is not meant for exposure to non-administrative users. This could eventually allow an authenticated attacker to write arbitrary files to the filesystem and indirectly achieve RCE. Users are recommended to upgrade to version 2.29.0 or later, which fixes the issue.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authorization
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that you perform access control checks related to your business logic. These checks may be different than the access control checks that you apply to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- lists.apache.org/thread/63b78shqz312phsx7v1ryr7jv7bprg58Issue Tracking, Mailing List
Other references
Other vulnerabilities in Apache ActiveMQ Artemis
- 9.1 Critical severity
- 9.8 Critical severity
- 9.1 Critical severity
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
Recent Improper Authorization vulnerabilities
- 8.3 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 7.5 High severity
Spotted an error? Tell us.