# CVE-2011-1460: Memory corruption in n/a

> A bad cast in WebKit allows attackers to execute arbitrary code via crafted web content in Google Chrome.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Nov 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4hxv-57v2-52jp

## What is CVE-2011-1460?

CVE-2011-1460 is a critical memory corruption vulnerability in n/a, published on 5 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WebKit in Google Chrome before Blink M11 contains a bad cast to RenderBlock when anonymous blocks are renderblocks.

Weakness: CWE-704 (Incorrect Type Conversion or Cast)

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

It affects 1 product.


Products: Google Blink.

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

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

## Is CVE-2011-1460 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-2337](https://insights.sbomify.com/CVE-2011-2337/): Integer overflow in Chrome on 64-bit platforms (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)
- [CVE-2011-1803](https://insights.sbomify.com/CVE-2011-1803/): Use after free in Chrome (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-1460 is a critical memory corruption vulnerability in n/a, published on 5 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-1460 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-1460/ (Markdown: https://insights.sbomify.com/CVE-2011-1460/index.md)
```

## Sources

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

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