# CVE-2011-2807: Other in Chrome

> Incorrect timer handling in WebKit can cause a denial of service in Google Chrome, requiring users to upgrade to a patched version.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **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:** 7 Nov 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v6jg-j6xh-j95v

## What is CVE-2011-2807?

CVE-2011-2807 is a medium-severity vulnerability in Google Chrome, published on 7 Nov 2019. 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

Incorrect handling of timer information in Timer.cpp in WebKit in Google Chrome before Blink M13.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

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

It affects 1 product.


Products: Google Blink.

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

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

## Is CVE-2011-2807 being exploited?

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

## Other vulnerabilities in Google Chrome

- [CVE-2011-2337](https://insights.sbomify.com/CVE-2011-2337/): Integer overflow in Chrome on 64-bit platforms (critical 9.8)
- [CVE-2011-1460](https://insights.sbomify.com/CVE-2011-1460/): Memory corruption in n/a (critical 9.8)
- [CVE-2011-2335](https://insights.sbomify.com/CVE-2011-2335/): Use after free in Chrome (high 7.5)
- [CVE-2011-1298](https://insights.sbomify.com/CVE-2011-1298/): Integer overflow in n/a (high 7.5)
- [CVE-2011-1802](https://insights.sbomify.com/CVE-2011-1802/): Memory corruption in Chrome (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-2807 is a medium-severity vulnerability in Google Chrome, published on 7 Nov 2019. 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-2807 in the wild and no public exploit code.

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

## Sources

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

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