CVE intelligence and bounded remediation

CVE-2018-6123 — Google Chrome security vulnerability

Medium CVSS 6.5

A use after free in Blink in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Severity
Medium
CVSS
6.5 (3.0)
Published
2019-01-09
CISA KEV
Not currently listed
Ecosystem
browser
Weaknesses
CWE-416, CWE-787

Affected products

  • google / chrome
  • debian / debian_linux / 9.0
  • redhat / enterprise_linux_desktop / 6.0
  • redhat / enterprise_linux_server / 6.0
  • redhat / enterprise_linux_workstation / 6.0

Matched remediation archetype

Buffer bounds, memory safety, and memory corruption

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Identify affected native-code versions, build flags, architectures, parsers, codecs, drivers, and input paths in all shipped artifacts.
  • Determine whether untrusted data reaches the affected routine and the process privilege, sandbox, and network exposure.
  • Confirm statically linked, vendored, firmware, and platform-provided copies, not only package-manager records.

Remediate safely

  • Apply the maintained upstream correction or replace the affected component, then rebuild every dependent artifact from clean inputs.
  • Adopt bounds-checked interfaces, validated sizes and integer conversions, clear ownership, and memory-safe components where practical.
  • Enable supported compiler and runtime hardening and add sanitized tests and fuzz regression seeds derived from non-weaponized fixtures.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.