# CVE-2013-1874: Path traversal in n/a

> Local attackers can execute arbitrary code by placing a malicious .csirc file in the current working directory, affecting Chicken Scheme users.

- **Severity:** Medium 4.4 (`AV:L/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:** 29 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-1874, GHSA-53x9-4x79-73hc

## What is CVE-2013-1874?

CVE-2013-1874 is a medium-severity path traversal vulnerability in n/a, published on 29 Sep 2014. 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

Untrusted search path vulnerability in csi in Chicken before 4.8.2 allows local users to execute arbitrary code via a Trojan horse .csirc in the current working directory.

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

It affects 1 product.


Products: Call-Cc Chicken.

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

Upgrade to a fixed version.

## Is CVE-2013-1874 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-45145](https://insights.sbomify.com/CVE-2022-45145/): Command injection in n/a (critical 9.8)
- [CVE-2014-6310](https://insights.sbomify.com/CVE-2014-6310/): Memory corruption in n/a (critical 9.8)
- [CVE-2012-6125](https://insights.sbomify.com/CVE-2012-6125/): Denial of service in chicken (critical 9.8)
- [CVE-2016-6830](https://insights.sbomify.com/CVE-2016-6830/): Memory corruption in n/a (critical 9.8)
- [CVE-2013-2024](https://insights.sbomify.com/CVE-2013-2024/): Command injection in chicken (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-1874 is a medium-severity path traversal vulnerability in n/a, published on 29 Sep 2014. 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-1874 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-1874/ (Markdown: https://insights.sbomify.com/CVE-2013-1874/index.md)
```

## Sources

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

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