# CVE-2007-4372: Other in n/a

> Unspecified remote vulnerability in NetWin SurgeMail with unknown impact, based on vague advisory data.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 16 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3mg7-6jfw-73pw

## What is CVE-2007-4372?

CVE-2007-4372 is a critical vulnerability in n/a, published on 16 Aug 2007. It can be exploited over the network.

### Official description

Unspecified vulnerability in NetWin SurgeMail 38k on Windows Server 2003 has unknown impact and remote attack vectors.  NOTE: this information is based upon a vague advisory by a vulnerability information sales organization that does not coordinate with vendors or release actionable advisories. A CVE has been assigned for tracking purposes, but duplicates with other CVEs are difficult to determine.

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

It affects 1 product.


Products: Netwin Surgemail.

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

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

## Is CVE-2007-4372 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-2537](https://insights.sbomify.com/CVE-2004-2537/): Other in n/a (critical 10.0)
- [CVE-2008-1497](https://insights.sbomify.com/CVE-2008-1497/): Memory corruption in n/a (critical 9.0)
- [CVE-2008-1498](https://insights.sbomify.com/CVE-2008-1498/): Memory corruption in n/a (critical 9.0)
- [CVE-2008-1055](https://insights.sbomify.com/CVE-2008-1055/): Other in n/a (high 7.5)
- [CVE-2007-2655](https://insights.sbomify.com/CVE-2007-2655/): Other in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4372 is a critical vulnerability in n/a, published on 16 Aug 2007. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2007-4372 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-4372/ (Markdown: https://insights.sbomify.com/CVE-2007-4372/index.md)
```

## Sources

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

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