# CVE-2013-2493: Denial of service in n/a

> A remote attacker can crash the browser via a crafted link, requiring user interaction to trigger the vulnerability.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/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:** 7 Mar 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6h7m-rmqf-vf77

## What is CVE-2013-2493?

CVE-2013-2493 is a medium-severity denial of service vulnerability in n/a, published on 7 Mar 2013. 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 Hook_Terminate function in chrome_frame/protocol_sink_wrap.cc in the Google Chrome Frame plugin before 26.0.1410.28 for Internet Explorer does not properly handle attach tab requests, which allows user-assisted remote attackers to cause a denial of service (application crash) via an _blank value for the target attribute of an A element.

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

## Which versions are affected by CVE-2013-2493?

It affects 1 product.


Products: Google Chrome Frame.

## How do I fix CVE-2013-2493?

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

## Is CVE-2013-2493 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2493 and fix it if it is affected.

What it is: CVE-2013-2493 is a medium-severity denial of service vulnerability in n/a, published on 7 Mar 2013. 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-2013-2493 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-2013-2493/ (Markdown: https://insights.sbomify.com/CVE-2013-2493/index.md)
```

## Sources

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

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