LiveActive security incident?Get immediate response
CVE Record

CVE-2023-0705: Integer overflow in Core in Google Chrome prior to 110.0.5481.77 allowed a remote attacker who had one a ra...

Integer overflow in Core in Google Chrome prior to 110.0.5481.77 allowed a remote attacker who had one a race condition to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Low)

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-0705 is a Chrome Core integer overflow fixed in Chrome 110.0.5481.77. A remote attacker could potentially trigger heap corruption through a crafted HTML page, but the source data says exploitation requires user interaction and a race condition, making reliable attack harder.

Executive priority

Treat this as a high-impact browser patching item, but not an emergency exploitation event based on the supplied evidence. Prioritize rapid cleanup of outdated Chrome installations, especially on user workstations exposed to untrusted web content.

Technical view

The flaw is CWE-190 integer overflow in Google Chrome Core before 110.0.5481.77. The CVSS vector is AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, reflecting network reachability, high attack complexity, no privileges, required user interaction, and potentially high confidentiality, integrity, and availability impact.

Likely exposure

Confirmed exposure is Chrome versions before 110.0.5481.77. Gentoo users should review GLSA-202309-17 for distribution packaging guidance. The bundle does not provide CPEs or a full downstream Chromium product list.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. Public description says a remote attacker would need a crafted HTML page and to win a race condition before potentially exploiting heap corruption.

Researcher notes

Severity signals differ: the CVE bundle gives CVSS 7.5 high, while the Chromium description labels security severity low. The bug tracker reference is included, but the supplied bundle does not provide exploitability details, proof of concept, or evidence of exploitation in the wild.

Mitigation direction

  • Update Chrome to 110.0.5481.77 or later.
  • Follow Gentoo GLSA-202309-17 where Gentoo packages are used.
  • Confirm managed browser update policies are enforcing supported versions.
  • Check vendor guidance for any downstream Chromium-based packaging details.

Validation and detection

  • Inventory Chrome versions across managed endpoints.
  • Flag any Chrome installation older than 110.0.5481.77.
  • Review browser management telemetry for update failures.
  • Verify Gentoo hosts against GLSA-202309-17 remediation status.
Prepared
Confidence
medium
Sources
5

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

CVE-2023-0705 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/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
4Source 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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H1.65.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2023-0705Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/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
GoogleChromeunspecifiedListed
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.