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

> Remote attackers can cause denial of service or execute arbitrary code on NetSupport Manager clients via crafted data during connection setup.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mjrx-98x2-x4rg

## What is CVE-2007-5252?

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

### Official description

Buffer overflow in NetSupport Manager (NSM) Client 10.00 and 10.20, and NetSupport School Student (NSS) 9.00, allows remote NSM servers to cause a denial of service or possibly execute arbitrary code via crafted data in the configuration exchange phase of an initial connection setup.  NOTE: a vendor statement, which is too vague to be sure that it is for this particular issue, says that only a denial of service is possible.

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

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

It affects 2 products.


Products: Netsupport Netsupport Manager Client, Netsupport Netsupport School Student.

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

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

## Is CVE-2007-5252 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-5057](https://insights.sbomify.com/CVE-2007-5057/): Auth bypass in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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