# CVE-2024-8287: Security feature bypass in Anbox Cloud

> An attacker can bypass TLS certificate validation in Anbox Cloud by performing a machine-in-the-middle attack on the internal network.

- **Severity:** High 7.5 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2024
- **Updated:** 19 Sep 2024
- **Also known as:** GHSA-vqjm-ch4v-x2f4

## What is CVE-2024-8287?

CVE-2024-8287 is a high-severity vulnerability in Canonical Ltd. Anbox Cloud, published on 18 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2024-8287?

It affects 1 product.


Products: Canonical Anbox Cloud.

## How do I fix CVE-2024-8287?

No fix has been published for CVE-2024-8287 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-8287 being exploited?

There is no known exploitation of CVE-2024-8287 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8287 and fix it if it is affected.

What it is: CVE-2024-8287 is a high-severity vulnerability in Canonical Ltd. Anbox Cloud, published on 18 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8287 in the wild and no public exploit code.

Affected product: Canonical Ltd. Anbox Cloud. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-8287/ (Markdown: https://insights.sbomify.com/CVE-2024-8287/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-8287
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-8287
- OSV: https://osv.dev/vulnerability/CVE-2024-8287

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-8287/
Summaries are generated and may contain mistakes; the official description above is the record.