LiveActive security incident?Get immediate response
CVE Record

CVE-2023-6345: Integer overflow in Skia in Google Chrome prior to 119.0.6045.199 allowed a remote attacker who had comprom...

Integer overflow in Skia in Google Chrome prior to 119.0.6045.199 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a malicious file. (Chromium security severity: High)

CriticalCVSS 9.6Known exploitedUpdated
Glexia's TakeHuman reviewedcritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-6345 is a serious Chrome graphics-library flaw that could let an attacker escape Chrome’s sandbox after already compromising the renderer process. The public record ties it to malicious file handling and CISA lists it as known exploited, so unmanaged or stale browser fleets need urgent attention.

Executive priority

Treat this as urgent endpoint hygiene. CISA KEV listing means exploitation is not theoretical, and a browser sandbox escape can materially raise the impact of web or file-based attacks. Patch and verify managed browsers promptly.

Technical view

The issue is a CWE-190 integer overflow in Skia affecting Google Chrome before 119.0.6045.199. The CVSS 3.1 vector is 9.6 critical, with network attack vector, user interaction required, changed scope, and high confidentiality, integrity, and availability impact after renderer compromise.

Likely exposure

Exposure is most likely on endpoints running Google Chrome before 119.0.6045.199. Linux environments using distributor Chromium packages should also verify Debian, Fedora, and Gentoo advisory coverage. The sources do not prove every Chromium-derived browser is affected, so validate each vendor separately.

Exploitation context

CISA KEV status supports known exploitation in the wild. The CVE description requires a compromised renderer process and a malicious file, so this should be treated as a post-renderer-compromise sandbox escape risk rather than a standalone initial-access bug.

Researcher notes

Evidence is strongest for Google Chrome before 119.0.6045.199 and distributor Chromium package advisories. Public details are limited, and the Chromium bug reference may restrict technical visibility. Avoid assuming exploit mechanics beyond renderer compromise, malicious file involvement, and sandbox escape potential.

Mitigation direction

  • Update Google Chrome to 119.0.6045.199 or later.
  • Apply Debian, Fedora, or Gentoo Chromium package updates where relevant.
  • Confirm managed browser update policies are enforcing the fixed version.
  • Check vendor guidance for any Chrome-derived browsers in use.
  • Prioritize internet-facing and high-risk user workstations.

Validation and detection

  • Inventory Chrome versions across managed endpoints.
  • Confirm all Chrome installations report 119.0.6045.199 or later.
  • Review Linux package versions against distributor advisories.
  • Check vulnerability scanner results for CVE-2023-6345 closure.
  • Verify browser restart completion after updates.
Prepared
Reviewed
Confidence
high
Sources
8

Michael Williams reviewed this cited source version on .

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.

cwe · low confidence lookup

CWE-190: 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 lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-6345 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
Critical
CVSS
9.6 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

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.

1CVSS vectors
0Timeline events
0ADP providers
9Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.6CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H2.86Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.6Critical
CVSS 3.1 vector shape for CVE-2023-6345Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleChrome119.0.6045.199Listed
Weakness

CWE details

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

CWE-190 · source CWE mapping

Integer Overflow or Wraparound

Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.