LiveActive security incident?Get immediate response
CVE Record

CVE-2023-7013: Inappropriate implementation in Compositing in Google Chrome prior to 119.0.6045.105 allowed a remote attac...

Inappropriate implementation in Compositing in Google Chrome prior to 119.0.6045.105 allowed a remote attacker to potentially spoof security UI via a crafted HTML page. (Chromium security severity: Medium)

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-7013 is a Chrome browser flaw that could let a malicious web page spoof security-related browser UI. The business risk is deception: users may trust a fake security signal and make unsafe decisions. The source bundle rates it medium severity and does not show known active exploitation.

Executive priority

Treat this as a routine but important browser patching issue. It is not documented as actively exploited, but UI spoofing can support phishing and fraud workflows, so delayed browser updates increase user-facing risk.

Technical view

Google describes this as an inappropriate implementation in Chrome Compositing before 119.0.6045.105. A remote attacker could potentially spoof security UI using a crafted HTML page. CVSS 3.1 is 5.4, with network attack vector, low complexity, no privileges, and required user interaction.

Likely exposure

Exposure is likely limited to users running Google Chrome versions before 119.0.6045.105. Managed desktop fleets, BYOD endpoints, and virtual desktops are relevant if browser patching was delayed or unmanaged.

Exploitation context

The source bundle does not identify active exploitation, and KEV is false. Exploitation would require a user to interact with attacker-controlled web content. The documented impact is potential security UI spoofing, not code execution or service disruption.

Researcher notes

Evidence is limited to the CVE description, CVSS data, CWE-1021, Chromium references, and Google release note. The public bundle names the issue class and fixed Chrome threshold but does not provide exploit details, indicators, or separate mitigations beyond updating.

Mitigation direction

  • Update Google Chrome to 119.0.6045.105 or later.
  • Confirm enterprise browser auto-update policies are enabled.
  • Prioritize unmanaged or internet-facing user endpoints.
  • Review Google Chrome release guidance for deployment details.
  • Recheck vendor guidance if supporting Chromium-based downstream browsers.

Validation and detection

  • Inventory Chrome versions across managed endpoints.
  • Flag Chrome versions earlier than 119.0.6045.105.
  • Verify update enforcement in browser management tooling.
  • Check whether vulnerable versions remain on BYOD or VDI images.
  • Document remediation status for affected user groups.
Prepared
Confidence
high
Sources
4

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.

cwe · low confidence lookup

CWE-1021: 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
cve · low confidence lookup

CVE-2023-7013 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
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

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
3Source links

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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-7013Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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.105Listed
Weakness

CWE details

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

CWE-1021 · source CWE mapping

Improper Restriction of Rendered UI Layers or Frames

Improper Restriction of Rendered UI Layers or Frames represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.