# CVE-2013-7069: Command injection in n/a

> Attackers can execute arbitrary code by tricking users into searching a directory containing a malicious .ackrc file with specific options.

- **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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h295-68h4-jx53, openSUSE-SU-2024:10014-1

## What is CVE-2013-7069?

CVE-2013-7069 is a medium-severity command injection vulnerability in n/a, published on 14 Dec 2013. 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

ack 2.00 through 2.11_02 allows remote attackers to execute arbitrary code via a (1) --pager, (2) --regex, or (3) --output option in a .ackrc file in a directory to be searched.

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

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ack` | openSUSE:Tumbleweed | All versions | 2.15_02-1.3 |

Products: Beyondgrep Ack.

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

Upgrade to a fixed version.

## Is CVE-2013-7069 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-7069 is a medium-severity command injection vulnerability in n/a, published on 14 Dec 2013. 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-2013-7069 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-7069/ (Markdown: https://insights.sbomify.com/CVE-2013-7069/index.md)
```

## Sources

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

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