# CVE-2012-2632: Security feature bypass in n/a

> Remote attackers can bypass URL restrictions on SEIL routers by exploiting improper CONNECT command handling when specific proxy features are enabled.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:N/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:** 15 Jun 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-56gp-rxr2-fq55

## What is CVE-2012-2632?

CVE-2012-2632 is a low-severity vulnerability in n/a, published on 15 Jun 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SEIL routers with firmware SEIL/x86 1.00 through 2.35, SEIL/X1 2.30 through 3.75, SEIL/X2 2.30 through 3.75, and SEIL/B1 2.30 through 3.75, when the http-proxy and application-gateway features are enabled, do not properly handle the CONNECT command, which allows remote attackers to bypass intended URL restrictions via a TCP session.

## Which versions are affected by CVE-2012-2632?

It affects 5 products.


Products: Seil B1, Seil B1 Firmware, Seil X1, Seil X2, Seil X86 Firmware.

## How do I fix CVE-2012-2632?

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

## Is CVE-2012-2632 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2632 and fix it if it is affected.

What it is: CVE-2012-2632 is a low-severity vulnerability in n/a, published on 15 Jun 2012. 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-2012-2632 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-2012-2632/ (Markdown: https://insights.sbomify.com/CVE-2012-2632/index.md)
```

## Sources

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

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