dbcve.org
Anbox CloudApplication · Canonical

CVE-2024-8287

HIGH · 7.5 CVSS v3.1 Published 2024-09-18
Fix available
A fix is available. Upgrade to 1.23.1 or later.
See remediation →
80/100
Remediation priority · High
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
Anbox Management Service, in versions 1.17.0 through 1.23.0, does not validate the TLS certificate provided to it by the Anbox Stream Agent. An attacker must be able to machine-in-the-middle the Anbox Stream Agent from within an internal network before they can attempt to take advantage of this.

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

The Anbox Management Service (versions 1.17.0-1.23.0) fails to validate TLS certificates presented by the Anbox Stream Agent during mutual TLS authentication. This allows an attacker with MITM positioning on the internal network to intercept and manipulate traffic between the management service and stream agent by presenting an invalid or attacker-controlled certificate.

MitigationEnable and enforce proper TLS certificate validation on the Anbox Management Service, ensuring it validates the complete certificate chain and hostname of the Anbox Stream Agent. Consider certificate pinning for added security.

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
Anbox CloudApplication
Affected:>= 1.17.0, < 1.23.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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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 Anbox Cloud version
    Query the Anbox Management Service version using 'anbox-cloud-version' or check the AMS container/package version. Common locations: /snap/anbox-cloud/current/manifest.yaml, 'anbox ams version' command, or the AMS API endpoint /1.0/version
    Affected if Version is 1.17.0 through 1.23.0 (anything >= 1.17.0 but < 1.23.1)
  2. Verify TLS certificate validation configuration
    Inspect the AMS configuration for TLS settings. Check if 'verify_client_cert', 'tls_verify', 'certificate_verification', or similar flags related to stream agent TLS validation are present and set to 'true' or 'enabled'. Look in AMS config files or environment variables
    Affected if TLS certificate validation is disabled, set to 'false', or missing for stream agent connections
  3. Check stream agent connection security settings
    Examine the Anbox Stream Agent configuration or the stream gateway settings that govern mutual TLS between AMS and the agent. Look for 'insecure_skip_verify', 'skip_tls_verify', or 'allow_insecure' parameters
    Affected if Certificate validation is explicitly skipped or set to insecure mode for stream agent communications
  4. Inspect certificate chain validation settings
    Review the AMS TLS/SSL configuration to determine if proper certificate chain validation is enforced. Check for any 'validate_cert_chain', 'verify_chain', or 'hostname_verification' settings
    Affected if Certificate chain or hostname validation is not enforced or is explicitly disabled

The environment is affected if Anbox Cloud version is between 1.17.0 and 1.23.0 AND TLS certificate validation for the Anbox Stream Agent is disabled or not properly configured in the Management Service.

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 1.23.1 or later
Fixed in 1.23.1
Interim mitigation

Enable and enforce proper TLS certificate validation on the Anbox Management Service, ensuring it validates the complete certificate chain and hostname of the Anbox Stream Agent. Consider certificate pinning for added security.

Recommended fix High confidence

1.23.1 or later

  1. 1. Identify the current Anbox Cloud version using 'anbox-cloud-version' or the dashboard
  2. 2. Review the Anbox Cloud upgrade documentation at https://anbox-cloud.io/docs/exp/upgrade
  3. 3. Create a backup of the current Anbox Cloud deployment configuration
  4. 4. Upgrade the Anbox Cloud deployment to version 1.23.1 or later following the documented procedure
  5. 5. Verify the upgrade was successful and the TLS certificate validation is now enforced
Caveat Review release notes for 1.23.1 for any configuration or API changes that may affect existing deployments

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

Fix this in Anbox Cloud 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-8287 — 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-8287 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