# CVE-2011-2602: Denial of service in n/a

> Remote attackers can crash the system via a crafted web page, requiring user interaction to visit the page.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:N/I:N/A:C`)
- **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:** 30 Jun 2011
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2gwv-c7j5-2654

## What is CVE-2011-2602?

CVE-2011-2602 is a high-severity denial of service vulnerability in n/a, published on 30 Jun 2011. 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 NVIDIA Geforce 310 driver 6.14.12.7061 on Windows XP SP3 allows remote attackers to cause a denial of service (system crash) via a crafted web page that is visited with Google Chrome or Mozilla Firefox, as demonstrated by the lots-of-polys-example.html test page in the Khronos WebGL SDK.

Weakness: CWE-399

## Which versions are affected by CVE-2011-2602?

It affects 1 product.


Products: Nvidia Geforce 310 Driver.

## How do I fix CVE-2011-2602?

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

## Is CVE-2011-2602 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2602 and fix it if it is affected.

What it is: CVE-2011-2602 is a high-severity denial of service vulnerability in n/a, published on 30 Jun 2011. 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-2011-2602 in the wild and no public exploit code.

Affected product: n/a. 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-2011-2602/ (Markdown: https://insights.sbomify.com/CVE-2011-2602/index.md)
```

## Sources

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

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