# CVE-2002-1599: Security feature bypass in n/a

> Remote attackers can bypass content filtering rules in DansGuardian by using hex-encoded URLs, 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:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Mar 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-3qxj-g3qm-3q3r

## What is CVE-2002-1599?

CVE-2002-1599 is a high-severity vulnerability in n/a, published on 13 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DansGuardian before 2.4.5-1 allows remote attackers to bypass content filtering rules via hex-encoded URLs.

## Which versions are affected by CVE-2002-1599?

It affects 1 product.


Products: Daniel Barron Dansguardian.

## How do I fix CVE-2002-1599?

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

## Is CVE-2002-1599 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-2065](https://insights.sbomify.com/CVE-2004-2065/): Security feature bypass in n/a (high 7.5)
- [CVE-2004-2282](https://insights.sbomify.com/CVE-2004-2282/): Path traversal in n/a (medium 5.0)
- [CVE-2004-2283](https://insights.sbomify.com/CVE-2004-2283/): Security feature bypass in n/a (medium 5.0)
- [CVE-2003-1506](https://insights.sbomify.com/CVE-2003-1506/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1599 and fix it if it is affected.

What it is: CVE-2002-1599 is a high-severity vulnerability in n/a, published on 13 Mar 2005. 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-2002-1599 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-2002-1599/ (Markdown: https://insights.sbomify.com/CVE-2002-1599/index.md)
```

## Sources

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

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