# CVE-2010-2363: Security feature bypass in n/a

> Remote attackers can bypass access restrictions on SEIL routers by spoofing IP addresses when strict IPv6 RPF is enabled.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Aug 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cgw6-gwvc-637r

## What is CVE-2010-2363?

CVE-2010-2363 is a medium-severity vulnerability in n/a, published on 30 Aug 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The IPv6 Unicast Reverse Path Forwarding (RPF) implementation on the SEIL/X1, SEIL/X2, and SEIL/B1 routers with firmware 1.00 through 2.73, when strict mode is used, does not properly drop packets, which might allow remote attackers to bypass intended access restrictions via a spoofed IP address.

Weakness: CWE-264

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

It affects 3 products.


Products: Iij Seil\/B1 Firmware, Iij Seil\/X1 Firmware, Iij Seil\/X2 Firmware.

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

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

## Is CVE-2010-2363 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2010-2363 is a medium-severity vulnerability in n/a, published on 30 Aug 2010. 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-2010-2363 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-2363/ (Markdown: https://insights.sbomify.com/CVE-2010-2363/index.md)
```

## Sources

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

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