# CVE-2009-1211: Security feature bypass in n/a

> Attackers can bypass proxy access controls and reach restricted intranet sites by exploiting transparent interception mode via crafted HTTP Host headers.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Apr 2009
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-j749-wjv7-4cf2

## What is CVE-2009-1211?

CVE-2009-1211 is a medium-severity vulnerability in n/a, published on 1 Apr 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Blue Coat ProxySG, when transparent interception mode is enabled, uses the HTTP Host header to determine the remote endpoint, which allows remote attackers to bypass access controls for Flash, Java, Silverlight, and probably other technologies, and possibly communicate with restricted intranet sites, via a crafted web page that causes a client to send HTTP requests with a modified Host header.

Weakness: CWE-16

## Which versions are affected by CVE-2009-1211?

It affects 19 products.


Products: Bluecoat Proxysg, Bluecoat Proxysg Sg210-10, Bluecoat Proxysg Sg210-25, Bluecoat Proxysg Sg210-5, Bluecoat Proxysg Sg510-10, Bluecoat Proxysg Sg510-20, Bluecoat Proxysg Sg510-25, Bluecoat Proxysg Sg510-5, Bluecoat Proxysg Sg810-10, Bluecoat Proxysg Sg810-20, Bluecoat Proxysg Sg810-25, Bluecoat Proxysg Sg810-5, Bluecoat Proxysg Sg9000-10, Bluecoat Proxysg Sg9000-20, Bluecoat Proxysg Sg9000-5, Bluecoat Proxysg Va-10, Bluecoat Proxysg Va-15, Bluecoat Proxysg Va-20, Bluecoat Proxysg Va-5.

## How do I fix CVE-2009-1211?

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

## Is CVE-2009-1211 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-5189](https://insights.sbomify.com/CVE-2010-5189/): Privilege escalation in n/a (critical 9.3)
- [CVE-2013-5959](https://insights.sbomify.com/CVE-2013-5959/): Denial of service in n/a (high 7.1)
- [CVE-2010-5190](https://insights.sbomify.com/CVE-2010-5190/): Security feature bypass in n/a (medium 5.0)
- [CVE-2010-5192](https://insights.sbomify.com/CVE-2010-5192/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1211 and fix it if it is affected.

What it is: CVE-2009-1211 is a medium-severity vulnerability in n/a, published on 1 Apr 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2009-1211 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-2009-1211/ (Markdown: https://insights.sbomify.com/CVE-2009-1211/index.md)
```

## Sources

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

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