# CVE-2013-1794: Memory corruption in n/a

> Remote authenticated users can trigger a buffer overflow in OpenAFS client utilities, causing a crash or potentially executing arbitrary code.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Mar 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-1794, GHSA-gjvw-c69w-xg78

## What is CVE-2013-1794?

CVE-2013-1794 is a medium-severity memory corruption vulnerability in n/a, published on 12 Mar 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in certain client utilities in OpenAFS before 1.6.2 allows remote authenticated users to cause a denial of service (crash) and possibly execute arbitrary code via a long fileserver ACL entry.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Openafs Openafs.

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

Upgrade to a fixed version.

## Is CVE-2013-1794 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-1251](https://insights.sbomify.com/CVE-2009-1251/): Memory corruption in n/a (critical 10.0)
- [CVE-2024-10394](https://insights.sbomify.com/CVE-2024-10394/): Theft of credentials in Unix client PAGs (high 8.4)
- [CVE-2024-10397](https://insights.sbomify.com/CVE-2024-10397/): Preallocated buffer overflows in XDR responses (high 7.7)
- [CVE-2019-18601](https://insights.sbomify.com/CVE-2019-18601/): Denial of service in n/a (high 7.5)
- [CVE-2011-0430](https://insights.sbomify.com/CVE-2011-0430/): Use after free in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-1794 is a medium-severity memory corruption vulnerability in n/a, published on 12 Mar 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-1794 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-1794/ (Markdown: https://insights.sbomify.com/CVE-2013-1794/index.md)
```

## Sources

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

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