# CVE-2007-5837: Command injection in n/a

> Remote attackers can execute arbitrary commands via shell metacharacters in feed links when Gnome URL handling is disabled.

- **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:** 5 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-1477-1, GHSA-cjcg-p99f-62w9

## What is CVE-2007-5837?

CVE-2007-5837 is a medium-severity command injection vulnerability in n/a, published on 5 Nov 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

GUI.pm in yarssr 0.2.2, when Gnome default URL handling is disabled, allows remote attackers to execute arbitrary commands via shell metacharacters in a link element in a feed.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Yarssr Yarssr.

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

Apply the vendor's patch.

## Is CVE-2007-5837 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-5837 exists.

Public exploit code:

- Yarssr 0.2.2 - GUI.PM Remote Code Injection (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5837 is a medium-severity command injection vulnerability in n/a, published on 5 Nov 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-5837 exists.

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-5837/ (Markdown: https://insights.sbomify.com/CVE-2007-5837/index.md)
```

## Sources

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

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