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

> Buffer overflows in Conquest allow remote attackers to execute arbitrary code or local users to gain privileges via malicious metaserver data.

- **Severity:** Medium 6.9 (`AV:L/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:** 10 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xh9x-w92m-2jwh

## What is CVE-2007-1371?

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

### Official description

Multiple buffer overflows in Conquest 8.2a and earlier (1) allow local users to gain privileges by querying a metaserver that sends a long server entry processed by metaGetServerList and allow remote metaservers to execute arbitrary code via a long server entry processed by metaGetServerList; (2) allow attackers to have an unknown impact by exceeding the configured number of metaservers; and allow remote attackers to corrupt memory via a SP_CLIENTSTAT packet with certain values of (3) unum or (4) snum, different vulnerabilities than CVE-2003-0933.

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

It affects 1 product.


Products: Radscan Conquest.

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

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

## Is CVE-2007-1371 being exploited?

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

Public exploit code:

- radscan conquest 8.2 - Multiple Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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