# CVE-2013-0758: Code injection in n/a

> Remote attackers can execute arbitrary JavaScript with chrome privileges via improper plugin and SVG interaction, requiring user interaction.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/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:** Yes
- **Published:** 13 Jan 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7p7h-fc6x-mhrh

## What is CVE-2013-0758?

CVE-2013-0758 is a critical code injection vulnerability in Canonical Ubuntu Linux, published on 13 Jan 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

Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderbird ESR 10.x before 10.0.12 and 17.x before 17.0.2, and SeaMonkey before 2.15 allow remote attackers to execute arbitrary JavaScript code with chrome privileges by leveraging improper interaction between plugin objects and SVG elements.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 14 products.


Products: Canonical Ubuntu Linux, Mozilla Firefox, Mozilla Seamonkey, Mozilla Thunderbird, Mozilla Thunderbird Esr, Opensuse Opensuse, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Workstation, Suse Linux Enterprise Desktop, Suse Linux Enterprise Server, Suse Linux Enterprise Software Development Kit.

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

Upgrade to a fixed version.

## Is CVE-2013-0758 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-0758 exists.

Public exploit code:

- Mozilla Firefox < 17.0.1 - Flash Privileged Code Injection (Metasploit) (exploitdb)
- Firefox 17.0.1 Flash Privileged Code Injection (metasploit)
- GIT 1.8.5.6/1.9.5/2.0.5/2.1.4/2.2.1 & Mercurial < 3.2.3 - Multiple Vulnerabilities (Metasploit) (exploitdb)

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0758 is a critical code injection vulnerability in Canonical Ubuntu Linux, published on 13 Jan 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-0758 exists.

Affected product: Canonical Ubuntu Linux. 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-0758/ (Markdown: https://insights.sbomify.com/CVE-2013-0758/index.md)
```

## Sources

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

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