# CVE-2007-3491: Memory corruption in n/a

> Remote attackers can exploit a buffer overflow in Progress OpenEdge via malformed TCP/IP messages, potentially leading to code execution or service disruption.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2crp-9jmr-vp26

## What is CVE-2007-3491?

CVE-2007-3491 is a high-severity memory corruption vulnerability in n/a, published on 29 Jun 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in _mprosrv in Progress Software OpenEdge before 9.1E0422, and 10.x before 10.1B01, allows remote attackers to have an unknown impact via a malformed TCP/IP message.

## Which versions are affected by CVE-2007-3491?

It affects 1 product.


Products: Progress Openedge.

## How do I fix CVE-2007-3491?

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

## Is CVE-2007-3491 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-1403](https://insights.sbomify.com/CVE-2024-1403/): Authentication Bypass in OpenEdge Authentication Gateway and AdminServer (critical 10.0)
- [CVE-2007-2417](https://insights.sbomify.com/CVE-2007-2417/): Memory corruption in n/a (critical 10.0)
- [CVE-2015-9245](https://insights.sbomify.com/CVE-2015-9245/): Misconfiguration in n/a (critical 9.8)
- [CVE-2023-40051](https://insights.sbomify.com/CVE-2023-40051/): Progress Application Server (PAS) for OpenEdge File Upload via Directory Traversal (critical 9.1)
- [CVE-2023-34203](https://insights.sbomify.com/CVE-2023-34203/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3491 and fix it if it is affected.

What it is: CVE-2007-3491 is a high-severity memory corruption vulnerability in n/a, published on 29 Jun 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-3491 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-2007-3491/ (Markdown: https://insights.sbomify.com/CVE-2007-3491/index.md)
```

## Sources

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

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