LiveActive security incident?Get immediate response
CVE Record

CVE-2023-2313: Inappropriate implementation in Sandbox in Google Chrome on Windows prior to 112.0.5615.49 allowed a remote...

Inappropriate implementation in Sandbox in Google Chrome on Windows prior to 112.0.5615.49 allowed a remote attacker who had compromised the renderer process to perform arbitrary read/write via a malicious file. (Chromium security severity: High)

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Chrome sandbox flaw affected Windows versions before 112.0.5615.49. If an attacker had already compromised Chrome's renderer process, a malicious file could let them perform arbitrary read/write operations, weakening the browser isolation model. The source bundle does not show CISA KEV listing or confirmed active exploitation.

Executive priority

Treat as high-priority browser patching. The requirement for prior renderer compromise lowers standalone urgency, but sandbox escapes matter because they can strengthen phishing or drive-by attack chains once another Chrome flaw is involved.

Technical view

CVE-2023-2313 is an inappropriate implementation issue in the Chrome Sandbox on Windows. The CVE states exploitation requires prior renderer compromise and interaction with a malicious file, then enables arbitrary read/write. Chromium rated it High. Public details are limited, and the linked Chromium bug may not provide full technical disclosure.

Likely exposure

Organizations with Google Chrome on Windows below 112.0.5615.49 are the clearest exposure. Fedora Chromium package advisories are referenced, so Linux package managers should also be checked where Chromium is deployed.

Exploitation context

The source bundle supports a chained-exploitation scenario, not a standalone browser compromise: the attacker first needs renderer compromise. No provided source establishes active exploitation, and the CVE is not marked KEV in the bundle.

Researcher notes

Do not assume public exploit availability from the provided evidence. Focus validation on version exposure and patch status. The key technical boundary is renderer-to-sandbox impact with arbitrary read/write via malicious file, but detailed root-cause mechanics are not disclosed in the bundle.

Mitigation direction

  • Update Google Chrome on Windows to 112.0.5615.49 or later.
  • Verify managed browser update policies are enforcing current stable releases.
  • Apply relevant Fedora Chromium package updates where those packages are deployed.
  • Check Google and distribution advisories for any newer vendor guidance.
  • Prioritize endpoints with internet-facing browsing or high-risk user groups.

Validation and detection

  • Inventory Chrome versions across Windows endpoints.
  • Confirm no managed device remains below 112.0.5615.49.
  • Review vulnerability scanner results for CVE-2023-2313.
  • Check Fedora systems for updated Chromium packages if applicable.
  • Document exceptions and compensating controls for unsupported endpoints.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cve · low confidence lookup

CVE-2023-2313 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleChrome112.0.5615.49Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.