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

> Remote attackers can execute arbitrary code via a stack-based buffer overflow in the Quiksoft EasyMail Objects IMAP4 component.

- **Severity:** High 7.6 (`AV:N/AC:H/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:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p94q-cj35-2pgh

## What is CVE-2007-1029?

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

### Official description

Stack-based buffer overflow in the Connect method in the IMAP4 component in Quiksoft EasyMail Objects before 6.5 allows remote attackers to execute arbitrary code via a long host name.

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

It affects 1 product.


Products: Quicksoft Easymail Objects.

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

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

## Is CVE-2007-1029 being exploited?

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

Public exploit code:

- EasyMail Objects 6.x - Connect Method Remote Stack Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1029 is a high-severity memory corruption vulnerability in n/a, published on 21 Feb 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-1029 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-2007-1029/ (Markdown: https://insights.sbomify.com/CVE-2007-1029/index.md)
```

## Sources

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

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