# CVE-2006-2920: Security feature bypass in n/a

> Remote attackers can bypass URI checks in Sylpheed clients by using leading spaces, facilitating phishing attacks against users.

- **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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2920, GHSA-pq2h-wp8j-q79c

## What is CVE-2006-2920?

CVE-2006-2920 is a low-severity vulnerability in n/a, published on 9 Jun 2006. 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

Sylpheed-Claws before 2.2.2 and Sylpheed before 2.2.6 allow remote attackers to bypass the URI check functionality and makes it easier to conduct phishing attacks via a URI that begins with a space character.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2006-2920?

It affects 2 products.


Products: Sylpheed-Claws Sylpheed-Claws, Sylpheed Sylpheed.

## How do I fix CVE-2006-2920?

Upgrade to a fixed version.

## Is CVE-2006-2920 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2958](https://insights.sbomify.com/CVE-2007-2958/): Code injection in n/a (medium 6.8)
- [CVE-2003-0852](https://insights.sbomify.com/CVE-2003-0852/): Other in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2920 and fix it if it is affected.

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

## Sources

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

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