Apache CloudStack: Incorrect Authorization
CVE-2024-42062 is a high-severity incorrect authorization vulnerability in Apache CloudStack from Apache, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. Affected Apache CloudStack versions: 4.10.0 through 4.18.2.2; 4.19.0.0 through 4.19.1.0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.95% chance of exploitation within 30 days, higher than 62% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Apache CloudStack you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on cloudstack.apache.org for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Apache | Apache CloudStack | 4.10.0 through 4.18.2.2; 4.19.0.0 through 4.19.1.0 | Not stated |
| Apache | cloudstack | 4.19.0.0 through 4.19.1.0; 4.10.0.0 through 4.18.2.2 | Not 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
- HighAdministrator-level access is required first.
- 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:H/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.2 | High | NVD |
| CVSS 3.1 | 7.2 | High | CISA (ADP) |
Official description
CloudStack account-users by default use username and password based authentication for API and UI access. Account-users can generate and register randomised API and secret keys and use them for the purpose of API-based automation and integrations. Due to an access permission validation issue that affects Apache CloudStack versions 4.10.0 up to 4.19.1.0, domain admin accounts were found to be able to query all registered account-users API and secret keys in an environment, including that of a root admin. An attacker who has domain admin access can exploit this to gain root admin and other-account privileges and perform malicious operations that can result in compromise of resources integrity and confidentiality, data loss, denial of service and availability of CloudStack managed infrastructure. Users are recommended to upgrade to Apache CloudStack 4.18.2.3 or 4.19.1.1, or later, which addresses this issue. Additionally, all account-user API and secret keys should be regenerated.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Authorization
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
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 access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied 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: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Patches and release notes
- lists.apache.org/thread/lxqtfd6407prbw3801hb4fz3ot3t8wljMailing List, Release Notes
Other references
Other vulnerabilities in Apache CloudStack
- 7.5 High severity
- 8.1 High severity
- 7.2 High severity
- 9.1 Critical severity
- 8.8 High severity
- 9.1 Critical severity
Recent Incorrect Authorization vulnerabilities
- 8.8 High severity
- 9.8 Critical severity
- 7.5 High severity
- 9.8 Critical severity
Apache OFBiz Incorrect Authorization Exploited
- 7.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.