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

> Remote attackers can cause a crash or execute arbitrary code via crafted email headers in Symantec Mail Security for SMTP.

- **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:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wppw-c5fq-jcc8

## What is CVE-2007-1252?

CVE-2007-1252 is a critical memory corruption vulnerability in n/a, published on 3 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in Symantec Mail Security for SMTP 5.0 before Patch 175 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via crafted headers in an e-mail message.  NOTE: some information was obtained from third party sources.

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

It affects 1 product.


Products: Symantec Mail Security.

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

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

## Is CVE-2007-1252 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-1792](https://insights.sbomify.com/CVE-2007-1792/): Denial of service in n/a (high 7.8)
- [CVE-2006-5545](https://insights.sbomify.com/CVE-2006-5545/): Business logic in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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