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

> Remote attackers can crash wpa_supplicant via crafted TSF data due to a stack-based buffer overflow in the driver_wext.c file.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rm2w-v49j-gx7w

## What is CVE-2007-6025?

CVE-2007-6025 is a high-severity memory corruption vulnerability in n/a, published on 19 Nov 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Stack-based buffer overflow in driver_wext.c in wpa_supplicant 0.6.0 and earlier allows remote attackers to cause a denial of service (crash) via crafted TSF data.

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

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

It affects 1 product.


Products: Wpa Supplicant Wpa Supplicant.

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

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

## Is CVE-2007-6025 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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