Chrome: Client-Side Enforcement of Server-Side Security
CVE-2022-3308 is a high-severity client-side enforcement of server-side security vulnerability in Chrome from Google, with a CVSS 3.1 base score of 7.4 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 106.0.5249.62 as the first without the flaw, so updating Chrome to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.83% chance of exploitation within 30 days, higher than 58% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Chrome to 106.0.5249.62 or a later version.
- Read the advisory on chromereleases.googleblog.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.4 | High | NVD |
| CVSS 3.1 | 7.4 | High | CISA (ADP) |
Official description
Insufficient policy enforcement in developer tools in Google Chrome prior to 106.0.5249.62 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Client-Side Enforcement of Server-Side Security
The product includes a server that relies on the client to implement a protection mechanism that is intended to protect the server.
How developers prevent this class of flaw
- If some degree of trust is required between the two entities, then use integrity checking and strong authentication to ensure that the inputs are coming from a trusted source. Design the product so that this trust is managed in a centralized fashion, especially if there are complex or numerous communication channels, in order to reduce the risks that the implementer will mistakenly omit a check in a single code path.
More Client-Side Enforcement of Server-Side Security vulnerabilities (CWE-602)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- chromereleases.googleblog.com/2022/09/stable-channel-update-for-desktop_27.htmlRelease Notes
- crbug.com/1342722Exploit, Issue Tracking
Other vulnerabilities in Chrome
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 7.5 High severity
Recent Client-Side Enforcement of Server-Side Security vulnerabilities
- 9.1 Critical severity
Spotted an error? Tell us.