# CVE-2017-5613: Code injection in n/a

> Remote attackers can execute arbitrary code via format string specifiers in template files within cgiemail and cgiecho utilities.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gh36-xvm9-3hm2, UBUNTU-CVE-2017-5613

## What is CVE-2017-5613?

CVE-2017-5613 is a high-severity code injection vulnerability in n/a, published on 3 Mar 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Format string vulnerability in cgiemail and cgiecho allows remote attackers to execute arbitrary code via format string specifiers in a template file.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2017-5613?

It affects 2 products.


Products: Cpanel Cgiecho, Cpanel Cgiemail.

## How do I fix CVE-2017-5613?

Apply the vendor's patch.

## Is CVE-2017-5613 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-5615](https://insights.sbomify.com/CVE-2017-5615/): Open redirect in n/a (medium 6.1)
- [CVE-2017-5616](https://insights.sbomify.com/CVE-2017-5616/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5613 and fix it if it is affected.

What it is: CVE-2017-5613 is a high-severity code injection vulnerability in n/a, published on 3 Mar 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-5613 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-2017-5613/ (Markdown: https://insights.sbomify.com/CVE-2017-5613/index.md)
```

## Sources

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

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