# CVE-2010-2522: Auth bypass in n/a

> Local attackers can spoof netlink messages in the UMIP mipv6 daemon due to missing origin verification, potentially leading to privilege escalation.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jul 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f7rp-3ppx-hhqw

## What is CVE-2010-2522?

CVE-2010-2522 is a low-severity authentication bypass vulnerability in n/a, published on 13 Jul 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The mipv6 daemon in UMIP 0.4 does not verify that netlink messages originated in the kernel, which allows local users to spoof netlink socket communication via a crafted unicast message.

Weakness: CWE-264

## Which versions are affected by CVE-2010-2522?

It affects 1 product.


Products: Linux-Ipv6 Umip.

## How do I fix CVE-2010-2522?

Apply the vendor's patch.

## Is CVE-2010-2522 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-2523](https://insights.sbomify.com/CVE-2010-2523/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2522 and fix it if it is affected.

What it is: CVE-2010-2522 is a low-severity authentication bypass vulnerability in n/a, published on 13 Jul 2010. 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-2010-2522 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-2010-2522/ (Markdown: https://insights.sbomify.com/CVE-2010-2522/index.md)
```

## Sources

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

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