dbcve.org
CloudstackApplication · Apache

CVE-2025-69233

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-08
Fix available
A fix is available. Upgrade to 4.20.3.0 / 4.22.0.1 or later.
See remediation →
59/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
Due to multiple time-of-check time-of-use race conditions in the resource count check and increment logic, as well as missing validations, users of the platform are able to exceed the allocation limits configured for their accounts/domains. This can be used by an attacker to degrade the infrastructure's resources and lead to denial of service conditions. Users are recommended to upgrade to Apache CloudStack versions 4.20.3.0 or 4.22.0.1, or later, which fixes this issue.

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 · moderate confidence

Apache CloudStack contains multiple time-of-check time-of-use (TOCTOU) race conditions in resource count validation and increment logic, combined with missing input validations. These flaws allow authenticated users to exceed configured allocation limits for their accounts/domains by exploiting the race between check and increment operations, potentially degrading infrastructure resources and causing denial of service.

MitigationUpgrade Apache CloudStack to version 4.20.3.0, 4.22.0.1, or later to patch the race conditions and missing validations in resource limit enforcement.

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.0.0, < 4.20.3.0>= 4.21.0.0, < 4.22.0.1

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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
    Run 'rpm -q cloudstack-management' on the management server host, or query the CloudStack API using the 'listVersions' command via the cloudmonkey CLI or direct API call to the management server
    Affected if The installed version is 4.0.0 <= version < 4.20.3.0 OR 4.21.0.0 <= version < 4.22.0.1
  2. Check if resource limits are configured for accounts or domains
    Query the CloudStack database: 'SELECT account, domain_id, resource_type, max FROM cloud.resource_limit;' or use the 'listResourceLimits' API command
    Affected if Any resource limits (cpu, memory, storage, etc.) are set for accounts or domains - the vulnerability allows bypassing these limits through race conditions
  3. Verify authenticated user access to the CloudStack API
    Confirm that the CloudStack management server API endpoint (port 8096 or 443) is accessible and that non-admin user accounts can authenticate via the 'login' API command
    Affected if Regular (non-root admin) user accounts exist and can authenticate - these users can exploit the TOCTOU race condition to exceed allocation limits
  4. Check for abnormal resource consumption patterns
    Review CloudStack usage records in the 'cloud.usage' and 'cloud.usage_event' tables, or monitor via 'listUsageRecords' API, looking for sudden spikes in resource creation that exceed configured limits
    Affected if Usage records show resource counts exceeding the configured limits for any account or domain

A user is affected if their CloudStack installation version falls within the vulnerable ranges AND they have resource limits configured AND authenticated users can access the API to trigger the race condition.

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.20.3.0 / 4.22.0.1 or later
Fixed in 4.20.3.04.22.0.1
Interim mitigation

Upgrade Apache CloudStack to version 4.20.3.0, 4.22.0.1, or later to patch the race conditions and missing validations in resource limit enforcement.

Recommended fix Moderate confidence

Apache CloudStack 4.20.3.0 or 4.22.0.1 (or later stable release)

  1. Review current Apache CloudStack installation to confirm the exact version running using 'cloudstack-sysvm' or management server logs
  2. Schedule a maintenance window for the upgrade process
  3. Take a complete backup of the CloudStack database and configuration files
  4. Download Apache CloudStack 4.20.3.0 or 4.22.0.1 (or later stable release) from the official Apache CloudStack repository
  5. Stop all CloudStack services on the management server(s) using 'cloudstack-management stop' or equivalent systemctl commands
  6. Upgrade the CloudStack packages using the appropriate package manager for your distribution (e.g., rpm or deb)
  7. Run database migration scripts if included in the upgrade (typically via 'cloudstack-management --setup-db')
  8. Start CloudStack management services and verify they are running
Caveat Review release notes for any database schema changes or configuration requirements between your current version and the target version before upgrading

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

Fix this in Cloudstack Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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