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

> Attackers can execute arbitrary commands on HP Linux Printing systems by injecting shell metacharacters into email from addresses processed by sendmail.

- **Severity:** High 7.6 (`AV:N/AC:H/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-5208, DSA-1462-1, DTSA-72-1, GHSA-qjxj-rc6r-r77w, RHSA-2007:0960, openSUSE-SU-2024:10847-1

## What is CVE-2007-5208?

CVE-2007-5208 is a high-severity command injection vulnerability in n/a, published on 13 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

hpssd in Hewlett-Packard Linux Imaging and Printing Project (hplip) 1.x and 2.x before 2.7.10 allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a from address, which is not properly handled when invoking sendmail.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `hpijs` | Red Hat:enterprise_linux:5::client | All versions | 1:1.6.7-4.1.el5_0.3 |
| `hplip` | Red Hat:enterprise_linux:5::client | All versions | 0:1.6.7-4.1.el5_0.3 |
| `hplip-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:1.6.7-4.1.el5_0.3 |
| `libsane-hpaio` | Red Hat:enterprise_linux:5::client | All versions | 0:1.6.7-4.1.el5_0.3 |
| `hpijs` | Red Hat:enterprise_linux:5::server | All versions | 1:1.6.7-4.1.el5_0.3 |
| `hplip` | Red Hat:enterprise_linux:5::server | All versions | 0:1.6.7-4.1.el5_0.3 |
| `hplip-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:1.6.7-4.1.el5_0.3 |
| `libsane-hpaio` | Red Hat:enterprise_linux:5::server | All versions | 0:1.6.7-4.1.el5_0.3 |
| `hplip` | openSUSE:Tumbleweed | All versions | 3.21.6-1.2 |

Products: Hp Linux Imaging and Printing Project.

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

Upgrade to a fixed version.

## Is CVE-2007-5208 being exploited?

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

Public exploit code:

- HPLIP hpssd.py From Address Arbitrary Command Execution (metasploit)
- hplip - 'hpssd.py' From Address Arbitrary Command Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-4267](https://insights.sbomify.com/CVE-2010-4267/): Memory corruption in n/a (high 7.5)
- [CVE-2008-2940](https://insights.sbomify.com/CVE-2008-2940/): Privilege escalation in n/a (high 7.2)
- [CVE-2013-4325](https://insights.sbomify.com/CVE-2013-4325/): Race condition in n/a (medium 6.9)
- [CVE-2013-6427](https://insights.sbomify.com/CVE-2013-6427/): Code injection in n/a (medium 6.8)
- [CVE-2011-2697](https://insights.sbomify.com/CVE-2011-2697/): Command injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5208 is a high-severity command injection vulnerability in n/a, published on 13 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-5208 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-5208/ (Markdown: https://insights.sbomify.com/CVE-2007-5208/index.md)
```

## Sources

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

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