# CVE-2003-0106: Security feature bypass in n/a

> Proxy users can bypass URL blocking filters in Symantec Enterprise Firewall by using encoded requests, allowing access to restricted content.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-3vmv-j634-9wxq

## What is CVE-2003-0106?

CVE-2003-0106 is a high-severity vulnerability in n/a, published on 27 Mar 2003. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The HTTP proxy for Symantec Enterprise Firewall (SEF) 7.0 allows proxy users to bypass pattern matching for blocked URLs via requests that are URL-encoded with escapes, Unicode, or UTF-8.

## Which versions are affected by CVE-2003-0106?

It affects 1 product.


Products: Symantec Enterprise Firewall.

## How do I fix CVE-2003-0106?

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

## Is CVE-2003-0106 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4422](https://insights.sbomify.com/CVE-2007-4422/): Information disclosure in n/a (critical 9.3)
- [CVE-2005-3768](https://insights.sbomify.com/CVE-2005-3768/): Memory corruption in n/a (high 7.5)
- [CVE-2002-1463](https://insights.sbomify.com/CVE-2002-1463/): Other in n/a (high 7.5)
- [CVE-2002-0538](https://insights.sbomify.com/CVE-2002-0538/): Server-side request forgery in n/a (high 7.5)
- [CVE-2002-2294](https://insights.sbomify.com/CVE-2002-2294/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0106 and fix it if it is affected.

What it is: CVE-2003-0106 is a high-severity vulnerability in n/a, published on 27 Mar 2003. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0106 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-2003-0106/ (Markdown: https://insights.sbomify.com/CVE-2003-0106/index.md)
```

## Sources

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

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