dbcve.org
CloudstackApplication · Apache

CVE-2024-41107

HIGH · 8.1 CVSS v3.1 Published 2024-07-19
Fix available
A fix is available. Upgrade to 4.18.2.2 / 4.19.1.0 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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 SAML authentication (disabled by default) does not enforce signature check. In CloudStack environments where SAML authentication is enabled, an attacker that initiates CloudStack SAML single sign-on authentication can bypass SAML authentication by submitting a spoofed SAML response with no signature and known or guessed username and other user details of a SAML-enabled CloudStack user-account. In such environments, this can result in a complete compromise of the resources owned and/or accessible by a SAML enabled user-account. Affected users are recommended to disable the SAML authentication plugin by setting the "saml2.enabled" global setting to "false", or upgrade to version 4.18.2.2, 4.19.1.0 or later, which addresses 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 · high confidence

CloudStack's SAML authentication plugin fails to validate signatures on SAML responses, allowing attackers to forge unsigned SAML responses and authenticate as any SAML-enabled user by knowing or guessing usernames.

MitigationDisable the SAML plugin by setting 'saml2.enabled' to 'false', or upgrade to patched versions 4.18.2.2/4.19.1.0 or later which enforce signature verification.

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.5.0, < 4.18.2.2>= 4.19.0.0, < 4.19.1.0

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 CloudStack version
    Run 'cloudmonkey' or check the management server JAR file version, or query the API: listCapabilities. The version is typically found in /usr/share/cloudstack-management/webapps/client/WEB-INF/lib or via the CloudStack UI footer.
    Affected if The installed version falls within >= 4.5.0 and < 4.18.2.2, OR >= 4.19.0.0 and < 4.19.1.0
  2. Verify SAML plugin is enabled
    Check the CloudStack configuration database or global settings for the 'saml2.enabled' parameter. Query: SELECT value FROM configuration WHERE name='saml2.enabled'; Or via API: listConfigurations with name='saml2.enabled'.
    Affected if The 'saml2.enabled' setting is set to 'true'
  3. Confirm SAML plugin is in use
    Check for existing SAML IdP metadata configured in CloudStack. Query: SELECT * FROM saml_identity_provider; Or verify that SAML SSO is listed as an authentication method in the login page configuration.
    Affected if SAML IdP metadata exists or SAML is listed as an active authentication provider

You are affected if your CloudStack version is vulnerable AND the SAML2 plugin is enabled and configured for user authentication.

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.2 / 4.19.1.0 or later
Fixed in 4.18.2.24.19.1.0
Interim mitigation

Disable the SAML plugin by setting 'saml2.enabled' to 'false', or upgrade to patched versions 4.18.2.2/4.19.1.0 or later which enforce signature verification.

Recommended fix High confidence

4.18.2.2 or 4.19.1.0 (or later)

  1. 1. Backup your current CloudStack configuration and database before proceeding with any upgrade.
  2. 2. Download the fixed release: upgrade to CloudStack 4.18.2.2 or 4.19.1.0 (or a later stable release in each respective branch).
  3. 3. If running CloudStack 4.5.0 through 4.18.x, upgrade to version 4.18.2.2.
  4. 4. If running CloudStack 4.19.0.0 through 4.19.0.x, upgrade to version 4.19.1.0 or later.
  5. 5. Follow the standard CloudStack upgrade procedure for your deployment type (basic, advanced, or managed).
  6. 6. After upgrade, verify SAML authentication now properly enforces signature validation.
  7. 7. Alternatively (if SAML is not needed), disable the SAML plugin by setting the global setting 'saml2.enabled' to 'false' in CloudStack configuration.
Caveat Review CloudStack release notes for your upgrade path to check for any migration steps or deprecated features between your current version and the target fixed version.

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

Fix this in Cloudstack Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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