dbcve.org
CloudstackApplication · Apache

CVE-2024-45461

MEDIUM · 6.3 CVSS v3.1 Published 2024-10-16
Fix available
A fix is available. Upgrade to 4.18.2.4 / 4.19.1.2 or later.
See remediation →
69/100
Remediation priority · Elevated
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
The CloudStack Quota feature allows cloud administrators to implement a quota or usage limit system for cloud resources, and is disabled by default. In environments where the feature is enabled, due to missing access check enforcements, non-administrative CloudStack user accounts are able to access and modify quota-related configurations and data. This issue affects Apache CloudStack from 4.7.0 through 4.18.2.3; and from 4.19.0.0 through 4.19.1.1, where the Quota feature is enabled. Users are recommended to upgrade to Apache CloudStack 4.18.2.4 or 4.19.1.2, or later, which addresses this issue. Alternatively, users that do not use the Quota feature are advised to disabled the plugin by setting the global setting "quota.enable.service" to "false".

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

Apache CloudStack's Quota feature, used for implementing resource usage limits, lacks proper access control enforcement. Non-administrative user accounts can access and modify quota-related configurations and data due to missing authorization checks, allowing privilege escalation in environments where the feature is enabled.

MitigationUpgrade to Apache CloudStack 4.18.2.4 or 4.19.1.2 or later to receive the access control fix, or alternatively disable the Quota plugin by setting the global setting 'quota.enable.service' to 'false' if the feature is not required.

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
CloudstackApplication
Affected:>= 4.7.0, < 4.18.2.4>= 4.19.0.0, < 4.19.1.2

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
Low
Integrity
Low
Availability
Low

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

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. Identify the installed Apache CloudStack version
    Locate the CloudStack management server version by checking the package version (e.g., rpm -q cloudstack-management) or via the CloudStack API using the 'listVersions' API command. Compare this version against the affected ranges: >= 4.7.0 and < 4.18.2.4, or >= 4.19.0.0 and < 4.19.1.2.
    Affected if The installed version falls within any of the affected version ranges.
  2. Verify if the Quota service is enabled
    Query the CloudStack global setting 'quota.enable.service' via the API using the 'listConfigurations' command with name='quota.enable.service', or review the configuration file on the management server.
    Affected if The configuration value is set to 'true' or is not explicitly set to 'false'.
  3. Confirm the Quota plugin is loaded
    Check if the Quota plugin is listed as an active service by invoking the 'listApis' command filtered for 'quota' or by reviewing the plugin registry if accessible through the admin interface.
    Affected if The Quota API commands are available and respond to non-administrative user accounts.
  4. Test non-administrative access to quota endpoints
    Using a non-admin user account, attempt to invoke quota-related API commands such as 'quotaUsage', 'quotaBalance', or 'quotaTemplate' to verify if authorization is enforced.
    Affected if Non-admin users can successfully execute quota API calls without receiving an authorization error.

A user is affected if their CloudStack installation runs an affected version AND has the Quota service enabled, allowing non-admin accounts to access quota operations.

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
Upgrade available Upgrade to 4.18.2.4 / 4.19.1.2 or later
Fixed in 4.18.2.44.19.1.2
Interim mitigation

Upgrade to Apache CloudStack 4.18.2.4 or 4.19.1.2 or later to receive the access control fix, or alternatively disable the Quota plugin by setting the global setting 'quota.enable.service' to 'false' if the feature is not required.

Recommended fix High confidence

Apache CloudStack 4.18.2.4 or 4.19.1.2 (or later)

  1. Plan and schedule a maintenance window for the CloudStack upgrade
  2. Backup the CloudStack database and all configuration files before proceeding
  3. Determine current version: if on 4.7.0 through 4.18.2.3, upgrade to 4.18.2.4; if on 4.19.0.0 through 4.19.1.1, upgrade to 4.19.1.2
  4. Download the appropriate Apache CloudStack release from the official Apache CloudStack repository
  5. Follow the official CloudStack upgrade guide to perform the upgrade
  6. After upgrade, verify the Quota service is functioning correctly and non-admin users can no longer access quota configurations
  7. As an alternative if the Quota feature is not needed, navigate to Global Settings and set 'quota.enable.service' to 'false', then restart the management server
Caveat Review release notes for migration considerations; test upgrade in non-production environment first

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

Fix this in Cloudstack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45461 — 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-2024-45461 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