# CVE-2009-1063: Memory corruption in n/a

> A buffer overflow in eXeScope allows remote attackers to execute arbitrary code by tricking users into opening a crafted executable file.

- **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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3f94-qwfc-p8gc

## What is CVE-2009-1063?

CVE-2009-1063 is a medium-severity memory corruption vulnerability in n/a, published on 24 Mar 2009. 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

Buffer overflow in eXeScope 6.50 allows user-assisted remote attackers to execute arbitrary code via a crafted executable (.exe) file.

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

## Which versions are affected by CVE-2009-1063?

It affects 1 product.


Products: Brother Soft Exescope.

## How do I fix CVE-2009-1063?

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

## Is CVE-2009-1063 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-1063 exists.

Public exploit code:

- eXeScope 6.50 - Local Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1063 and fix it if it is affected.

What it is: CVE-2009-1063 is a medium-severity memory corruption vulnerability in n/a, published on 24 Mar 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-1063 exists.

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-2009-1063/ (Markdown: https://insights.sbomify.com/CVE-2009-1063/index.md)
```

## Sources

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

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