# CVE-2014-2720: Code injection in n/a

> Attackers can execute arbitrary code by spoofing file extensions in ZIP archives, tricking users into opening malicious files disguised as safe images.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/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:** 27 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9hq8-hvqw-5h33

## What is CVE-2014-2720?

CVE-2014-2720 is a medium-severity code injection vulnerability in n/a, published on 27 May 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

IZArc 4.1.8 displays a file's name on the basis of a ZIP archive's Central Directory entry, but launches this file on the basis of a ZIP archive's local file header, which allows user-assisted remote attackers to conduct file-extension spoofing attacks via a modified Central Directory, as demonstrated by unintended code execution prompted by a .jpg extension in the Central Directory and a .exe extension in the local file header.

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

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

It affects 1 product.


Products: Izarc Izarc.

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

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

## Is CVE-2014-2720 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-5235](https://insights.sbomify.com/CVE-2010-5235/): Path traversal in n/a (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2720 is a medium-severity code injection vulnerability in n/a, published on 27 May 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-2720 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-2014-2720/ (Markdown: https://insights.sbomify.com/CVE-2014-2720/index.md)
```

## Sources

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

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