Improper certificate validation in Canonical Anbox Cloud
Priority LOW 34CWE-295Published · Updated
Key facts
- Attack vector
- Adjacent network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-295.
Summary
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.
Why it matters now
Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00176 7th percentileScored 2026-11-07
Fix Fixed Anbox Cloud (Canonical Ltd.): 1.23.1
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA Anbox Cloud (Canonical Ltd.) Fixed in 1.23.1
Timeline
- 2026-10-02 Threatist record created from CVE-2024-8287
- 2026-10-03 Alias added: GHSA-vqjm-ch4v-x2f4
References
Sources
- CVE-2024-8287 · CVE Program
- CVE-2024-8287 · NVD
- FIRST EPSS
- GHSA-vqjm-ch4v-x2f4 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences