# CVE-2014-2018: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML into email clients via crafted data URLs in OBJECT or EMBED elements, requiring user interaction to view the message.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **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:** 17 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r5wp-hg7f-vr2m

## What is CVE-2014-2018?

CVE-2014-2018 is a medium-severity cross-site scripting vulnerability in Mozilla Seamonkey, published on 17 Feb 2014. 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

Cross-site scripting (XSS) vulnerability in Mozilla Thunderbird 17.x through 17.0.8, Thunderbird ESR 17.x through 17.0.10, and SeaMonkey before 2.20 allows user-assisted remote attackers to inject arbitrary web script or HTML via an e-mail message containing a data: URL in a (1) OBJECT or (2) EMBED element, a related issue to CVE-2013-6674.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2014-2018?

It affects 3 products.


Products: Mozilla Seamonkey, Mozilla Thunderbird, Mozilla Thunderbird Esr.

## How do I fix CVE-2014-2018?

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

## Is CVE-2014-2018 being exploited?

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

## Other vulnerabilities in Mozilla Seamonkey

- [CVE-2008-4070](https://insights.sbomify.com/CVE-2008-4070/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-4571](https://insights.sbomify.com/CVE-2006-4571/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-2210](https://insights.sbomify.com/CVE-2009-2210/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-1282](https://insights.sbomify.com/CVE-2007-1282/): Integer overflow in n/a (critical 9.3)
- [CVE-2008-0304](https://insights.sbomify.com/CVE-2008-0304/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2018 and fix it if it is affected.

What it is: CVE-2014-2018 is a medium-severity cross-site scripting vulnerability in Mozilla Seamonkey, published on 17 Feb 2014. 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-2014-2018 in the wild and no public exploit code.

Affected product: Mozilla Seamonkey. 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-2014-2018/ (Markdown: https://insights.sbomify.com/CVE-2014-2018/index.md)
```

## Sources

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

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