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

> Remote attackers can bypass IP and domain restrictions and corrupt logs by spoofing X-Forwarded-For headers in Bloxx Web Filtering.

- **Severity:** Medium 5.0 (`AV:N/AC:L/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:** 9 Jun 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-49fq-7r6m-vrr7

## What is CVE-2012-2566?

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

### Official description

Bloxx Web Filtering before 5.0.14 does not properly interpret X-Forwarded-For headers during access-control and logging operations for HTTPS connection attempts, which allows remote attackers to bypass intended IP address and domain restrictions, and trigger misleading log entries, via a crafted header.

Weakness: CWE-264

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

It affects 1 product.


Products: Bloxx Web Filtering.

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

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

## Is CVE-2012-2566 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-2564](https://insights.sbomify.com/CVE-2012-2564/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2012-3343](https://insights.sbomify.com/CVE-2012-3343/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2012-2565](https://insights.sbomify.com/CVE-2012-2565/): Weak cryptography in n/a (medium 5.8)
- [CVE-2012-2563](https://insights.sbomify.com/CVE-2012-2563/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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