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

> Heap-based buffer overflow in Oracle Outside In Technology allows attackers to cause denial of service or execute code via crafted Paradox database files.

- **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 stated
- **Attackable:** Not stated
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jan 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rw5c-c8fm-hmv6

## What is CVE-2013-0418?

CVE-2013-0418 is a medium-severity memory corruption vulnerability in Microsoft Exchange Server, published on 17 Jan 2013. 

### Official description

Unspecified vulnerability in the Oracle Outside In Technology component in Oracle Fusion Middleware 8.3.7 and 8.4 allows context-dependent attackers to affect availability via unknown vectors related to Outside In Filters, a different vulnerability than CVE-2013-0393.  NOTE: the previous information was obtained from the January 2013 CPU.  Oracle has not commented on claims from an independent researcher that this is a heap-based buffer overflow in the Paradox database stream filter (vspdx.dll) that can be triggered using a table header with a crafted "number of fields" value.

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

It affects 2 products.


Products: Microsoft Exchange Server, Oracle Fusion Middleware.

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

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

## Is CVE-2013-0418 being exploited?

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

## Other vulnerabilities in Microsoft Exchange Server

- [CVE-2024-21410](https://insights.sbomify.com/CVE-2024-21410/): Microsoft Exchange Server Privilege Escalation (critical 9.8, exploited in the wild)
- [CVE-2021-34473](https://insights.sbomify.com/CVE-2021-34473/): Microsoft Exchange Server Remote Code Execution (critical 9.1, exploited in the wild)
- [CVE-2021-26855](https://insights.sbomify.com/CVE-2021-26855/): Microsoft Exchange Server Remote Code Execution (critical 9.1, exploited in the wild)
- [CVE-2021-34523](https://insights.sbomify.com/CVE-2021-34523/): Microsoft Exchange Server Privilege Escalation (critical 9.0, exploited in the wild)
- [CVE-2023-21529](https://insights.sbomify.com/CVE-2023-21529/): Microsoft Exchange Server Deserialization of Untrusted Data (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0418 is a medium-severity memory corruption vulnerability in Microsoft Exchange Server, published on 17 Jan 2013. 
Exploitation: There is no known exploitation of CVE-2013-0418 in the wild and no public exploit code.

Affected product: Microsoft Exchange Server. 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-0418/ (Markdown: https://insights.sbomify.com/CVE-2013-0418/index.md)
```

## Sources

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

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