# CVE-2007-2958: Code injection in n/a

> Remote POP3 servers can execute arbitrary code on Sylpheed clients via format string vulnerabilities in error handling.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-2958, GHSA-cjx9-q8g7-cf62

## What is CVE-2007-2958?

CVE-2007-2958 is a medium-severity code injection vulnerability in n/a, published on 27 Aug 2007. 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

Format string vulnerability in the inc_put_error function in src/inc.c in Sylpheed 2.4.4, and Sylpheed-Claws (Claws Mail) 1.9.100 and 2.10.0, allows remote POP3 servers to execute arbitrary code via format string specifiers in crafted replies.

## Which versions are affected by CVE-2007-2958?

It affects 2 products.


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

## How do I fix CVE-2007-2958?

Upgrade to a fixed version.

## Is CVE-2007-2958 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0852](https://insights.sbomify.com/CVE-2003-0852/): Other in n/a (medium 5.0)
- [CVE-2006-2920](https://insights.sbomify.com/CVE-2006-2920/): Security feature bypass in n/a (low 2.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2958 and fix it if it is affected.

What it is: CVE-2007-2958 is a medium-severity code injection vulnerability in n/a, published on 27 Aug 2007. 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-2007-2958 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-2007-2958/ (Markdown: https://insights.sbomify.com/CVE-2007-2958/index.md)
```

## Sources

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

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