Security readout for executives and security teams
Plain-English summary
This Chrome issue let a malicious web page bypass browser same-origin protections and configured proxy settings through DevTools behavior in versions before 110.0.5481.77. It required user interaction and was rated Low by Chromium, but CVSS emphasizes integrity impact. Treat it as a browser fleet patch-compliance issue, not an emergency absent exploitation evidence.
Executive priority
Prioritize routine-to-expedited browser patching, especially for managed endpoints handling sensitive workflows or enforced proxy routing. This is not source-supported as actively exploited, but browser flaws can scale quickly when fleets lag behind automatic updates.
Technical view
CVE-2023-0704 is insufficient policy enforcement in Google Chrome DevTools before 110.0.5481.77. A remote attacker could use a crafted HTML page to bypass same origin policy and proxy settings. The CVSS vector is network reachable, low complexity, no privileges, user interaction required, unchanged scope, high integrity impact.
Likely exposure
Exposure is most likely on unmanaged or slow-patching desktop Chrome or Chromium installations older than 110.0.5481.77. The provided data names Google Chrome and Gentoo’s Chromium advisory; it does not prove exposure for other Chromium-based browsers.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. The issue is remotely triggerable but requires user interaction with attacker-controlled content. Public details are limited, including the Chromium bug reference, so do not assume exploit availability from these sources alone.
Researcher notes
The key security property impact is policy bypass in DevTools affecting same-origin and proxy controls. Evidence is sparse beyond the CVE text, Chrome stable release note, and Gentoo advisory. Avoid broad product conclusions unless a vendor explicitly maps this CVE to its browser or package.
Mitigation direction
- Update Google Chrome to 110.0.5481.77 or later.
- Apply relevant Chromium package updates from your Linux distribution.
- Use enterprise browser management to enforce minimum patched versions.
- Review Google and distribution advisories for any superseding guidance.
Validation and detection
- Inventory Chrome and Chromium versions across managed endpoints.
- Flag installations older than 110.0.5481.77 for remediation.
- Check Gentoo systems against GLSA-202309-17 package guidance.
- Confirm browser update policies are active and reporting compliance.
- Monitor vendor advisories and KEV for changed exploitation status.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-602: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-0704 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://chromereleases.googleblog.com/2023/02/stable-channel-update-for-desktop.htmlCVE reference
- https://crbug.com/1385982CVE reference
- GLSA-202309-17CVE reference · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Client-Side Enforcement of Server-Side Security
Client-Side Enforcement of Server-Side Security represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.