dbcve.org
Azure CyclecloudApplication · Microsoft

CVE-2024-43602

CRITICAL · 9.9 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 8.6.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

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
Azure CycleCloud Remote Code Execution Vulnerability

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

Azure CycleCloud contains a remote code execution vulnerability that allows attackers to execute arbitrary code on affected installations. The critical severity (CVSS 9.9) indicates trivial exploitability with complete system compromise potential.

MitigationApply Microsoft security updates for Azure CycleCloud as they become available. Restrict network exposure of CycleCloud management interfaces to authorized administrative networks.

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
Azure CyclecloudApplication
Affected:>= 8.0.0, < 8.6.5

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 Azure CycleCloud installation
    Locate the Azure CycleCloud installation directory or check for the CycleCloud CLI/management interface. On the CycleCloud server, typical locations include /opt/cyclecloud or C:\CycleCloud. Use 'cyclecloud --version' or check cyclecloud_app.conf if available.
    Affected if Azure CycleCloud is installed and running
  2. Retrieve the installed version number
    Run 'cyclecloud --version' from the command line, or inspect the cyclecloud_app.conf version file in the installation directory. The version is typically displayed in the management UI footer or obtained via 'cyclecloud get_version'.
    Affected if Version cannot be determined or the command fails (may indicate no CycleCloud installation)
  3. Compare version against affected range
    Compare the installed version to the vulnerable range: 8.0.0 <= version < 8.6.5. If the version is 8.6.5 or higher, it is not affected. If it is 8.0.0 or higher but below 8.6.5, it is vulnerable.
    Affected if Installed version falls within 8.0.0 through 8.6.4 (inclusive)
  4. Verify network exposure of management interfaces
    Review firewall rules, network security groups, or CycleCloud cluster network configuration to determine if the CycleCloud management interface (typically port 8443) is exposed to untrusted networks or the public internet.
    Affected if Management interface is accessible from untrusted networks (this increases exploitability but does not change the vulnerable version status)

Your environment is affected if Azure CycleCloud version 8.0.0 through 8.6.4 is installed, regardless of network configuration, as the RCE vulnerability is present in these versions.

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 8.6.5 or later
Fixed in 8.6.5
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply Microsoft security updates for Azure CycleCloud as they become available. Restrict network exposure of CycleCloud management interfaces to authorized administrative networks.

Recommended fix Moderate confidence

8.6.5

  1. 1. Review the current Azure CycleCloud installation to confirm the exact version (can be done via CycleCloud CLI: cyclecloud show cluster <cluster_name> or via the CycleCloud web UI)
  2. 2. Plan the upgrade during a maintenance window as per Azure CycleCloud upgrade documentation
  3. 3. If using Azure CycleCloud on Azure, follow the Azure upgrade procedures documented at https://learn.microsoft.com/en-us/azure/cyclecloud/overview
  4. 4. For self-hosted Azure CycleCloud, download and install version 8.6.5 or later from the official Microsoft Azure CycleCloud download location
  5. 5. After upgrade, verify the CycleCloud service is running and accessible
  6. 6. Validate that all clusters can be managed properly post-upgrade

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

Fix this in Azure Cyclecloud Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA12.0 h
60.0 hours of engineering $10,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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