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

> An off-by-one error in the GeoIP module allows attackers to execute arbitrary code or cause denial of service via buffer overflow.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5p6w-mpm7-9f76

## What is CVE-2007-5713?

CVE-2007-5713 is a high-severity memory corruption vulnerability in n/a, published on 30 Oct 2007. It can be exploited over the network, with no action from the victim.

### Official description

Off-by-one error in the GeoIP module in the AMX Mod X 1.76d plugin for Half-Life Server might allow attackers to execute arbitrary code or cause a denial of service via unspecified input related to geolocation, which triggers an error message from the (1) geoip_code2 or (2) geoip_code3 function, leading to a buffer overflow.

Weakness: CWE-189

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

It affects 2 products.


Products: Amxmodx Amx Mod X, Valve Software Half-Life Dedicated Server.

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

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

## Is CVE-2007-5713 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5713 is a high-severity memory corruption vulnerability in n/a, published on 30 Oct 2007. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-5713 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-5713/ (Markdown: https://insights.sbomify.com/CVE-2007-5713/index.md)
```

## Sources

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

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