dbcve.org
ChromeWeb browser · Google

CVE-2023-1530

HIGH · 8.8 CVSS v3.1 Published 2023-03-21
Fix available
A fix is available. Upgrade to 111.0.5563.110 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Use after free in PDF in Google Chrome prior to 111.0.5563.110 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Use-after-free vulnerability in Google Chrome's PDF rendering component prior to version 111.0.5563.110 allows remote attackers to exploit heap corruption via a specially crafted HTML page containing malicious PDF content.

MitigationUpdate Google Chrome to version 111.0.5563.110 or later to patch the vulnerability; enterprise deployments may require coordinated browser update deployment across managed endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 111.0.5563.110
FedoraOperating system
Affected:= 36= 37= 38

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine if Google Chrome is installed
    Check for the Chrome executable: on Windows look in Program Files/Google/Chrome/Application/, on macOS look in /Applications/Google Chrome.app/, on Linux check for /usr/bin/google-chrome or /usr/bin/chromium-browser
    Affected if Google Chrome is not present on the system, then the CVE does not apply
  2. Retrieve the installed Chrome version number
    Open chrome://version in the Chrome browser address bar, or run 'google-chrome --version' from command line, or on Linux check the RPM package with 'rpm -q google-chrome'
    Affected if The command fails or returns no version, meaning Chrome may not be properly installed
  3. Compare installed version against the affected range
    Compare the version from step 2 to 111.0.5563.110 - any version below 111.0.5563.110 is affected (for example 111.0.5563.64 or 110.0.5481.177)
    Affected if The installed version is less than 111.0.5563.110 (for example showing 111.0.5563.64 or any earlier version)
  4. For Fedora systems, verify the package version
    On Fedora systems run 'rpm -q google-chrome' to see the installed package version, or 'dnf list installed google-chrome'
    Affected if Running Fedora 36, 37, or 38 with a google-chrome package version below the fixed release for that distribution

A user is affected if Google Chrome is installed with a version lower than 111.0.5563.110 (or the equivalent patched package version on Fedora 36/37/38), and the user could potentially open a maliciously crafted HTML file containing PDF content in the browser.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 111.0.5563.110 or later
Fixed in 111.0.5563.110
Interim mitigation

Update Google Chrome to version 111.0.5563.110 or later to patch the vulnerability; enterprise deployments may require coordinated browser update deployment across managed endpoints.

Recommended fix High confidence

Chrome 111.0.5563.110

  1. Update Google Chrome to version 111.0.5563.110 or later by navigating to chrome://settings/help and clicking 'Update Google Chrome', or by downloading the latest version from the official Chrome download page

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-1530 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-1530 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data