# CVE-2014-1710: Memory corruption in n/a

> Remote attackers can cause denial of service or potential code execution via GPU command-buffer memory corruption in Google Chrome.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rjp2-cf2f-33w2

## What is CVE-2014-1710?

CVE-2014-1710 is a high-severity memory corruption vulnerability in Google Chrome Os, published on 16 Mar 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The AsyncPixelTransfersCompletedQuery::End function in gpu/command_buffer/service/query_manager.cc in Google Chrome, as used in Google Chrome OS before 33.0.1750.152, does not check whether a certain position is within the bounds of a shared-memory segment, which allows remote attackers to cause a denial of service (GPU command-buffer memory corruption) or possibly have unspecified other impact via unknown vectors.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2014-1710?

It affects 1 product.


Products: Google Chrome Os.

## How do I fix CVE-2014-1710?

No fix has been published for CVE-2014-1710 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-1710 being exploited?

There is no known exploitation of CVE-2014-1710 in the wild and no public exploit code.

## Other vulnerabilities in Google Chrome Os

- [CVE-2014-1708](https://insights.sbomify.com/CVE-2014-1708/): Code injection in n/a (critical 10.0)
- [CVE-2013-2833](https://insights.sbomify.com/CVE-2013-2833/): Use after free in n/a (critical 10.0)
- [CVE-2013-0915](https://insights.sbomify.com/CVE-2013-0915/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2864](https://insights.sbomify.com/CVE-2012-2864/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-4050](https://insights.sbomify.com/CVE-2012-4050/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-1710 and fix it if it is affected.

What it is: CVE-2014-1710 is a high-severity memory corruption vulnerability in Google Chrome Os, published on 16 Mar 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-1710 in the wild and no public exploit code.

Affected product: Google Chrome Os. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-1710/ (Markdown: https://insights.sbomify.com/CVE-2014-1710/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-1710
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-1710
- OSV: https://osv.dev/vulnerability/CVE-2014-1710

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-1710/
Summaries are generated and may contain mistakes; the official description above is the record.