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

> Remote attackers can execute arbitrary code or cause denial of service via a crafted Access file, requiring user interaction to open the file.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 11 Sep 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x9rc-5q22-7m3g

## What is CVE-2013-3157?

CVE-2013-3157 is a critical memory corruption vulnerability in n/a, published on 11 Sep 2013. 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

Microsoft Access 2007 SP3, 2010 SP1 and SP2, and 2013 in Microsoft Office allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted Access file, aka "Access Memory Corruption Vulnerability," a different vulnerability than CVE-2013-3155.

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

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

It affects 1 product.


Products: Microsoft Access.

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

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

## Is CVE-2013-3157 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0671](https://insights.sbomify.com/CVE-2007-0671/): Microsoft Office Excel Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2000-0788](https://insights.sbomify.com/CVE-2000-0788/): Code injection in n/a (critical 10.0)
- [CVE-2015-2503](https://insights.sbomify.com/CVE-2015-2503/): Security feature bypass in n/a (critical 9.3)
- [CVE-2013-3155](https://insights.sbomify.com/CVE-2013-3155/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-3156](https://insights.sbomify.com/CVE-2013-3156/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-3157 is a critical memory corruption vulnerability in n/a, published on 11 Sep 2013. 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-2013-3157 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-3157/ (Markdown: https://insights.sbomify.com/CVE-2013-3157/index.md)
```

## Sources

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

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