# CVE-2022-41751: Command injection in n/a

> Attackers can execute arbitrary OS commands via malicious JPEG filenames when using the regeneration option in Jhead.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Oct 2022
- **Updated:** 13 May 2025
- **Also known as:** DEBIAN-CVE-2022-41751, GHSA-8m3f-vphm-cjhj, UBUNTU-CVE-2022-41751, openSUSE-SU-2022:10178-1, openSUSE-SU-2022:10179-1, openSUSE-SU-2023:0054-1, openSUSE-SU-2023:0371-1, openSUSE-SU-2024:12466-1

## What is CVE-2022-41751?

CVE-2022-41751 is a high-severity command injection vulnerability in Debian Debian Linux, published on 17 Oct 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Jhead 3.06.0.1 allows attackers to execute arbitrary OS commands by placing them in a JPEG filename and then using the regeneration -rgt50 option.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2022-41751?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jhead` | SUSE:Package Hub 15 SP3 | All versions | 3.00-bp153.3.3.1 |
| `jhead` | SUSE:Package Hub 15 SP4 | All versions | 3.06.0.1-bp154.2.3.1 |
| `jhead` | SUSE:Package Hub 15 SP4 | All versions | 3.06.0.1-bp154.2.9.1 |
| `jhead` | SUSE:Package Hub 15 SP5 | All versions | 3.06.0.1-bp155.5.3.1 |
| `jhead` | openSUSE:Leap 15.3 | All versions | 3.00-bp153.3.3.1 |
| `jhead` | openSUSE:Leap 15.4 | All versions | 3.06.0.1-bp154.2.3.1 |
| `jhead` | openSUSE:Leap 15.4 | All versions | 3.06.0.1-bp154.2.9.1 |
| `jhead` | openSUSE:Leap 15.5 | All versions | 3.06.0.1-bp155.5.3.1 |
| `jhead` | openSUSE:Tumbleweed | All versions | 3.06.0.1-2.1 |

Products: Debian Debian Linux, Fedoraproject Fedora, Jhead Project Jhead.

## How do I fix CVE-2022-41751?

Apply the vendor's patch.

## Is CVE-2022-41751 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41751 and fix it if it is affected.

What it is: CVE-2022-41751 is a high-severity command injection vulnerability in Debian Debian Linux, published on 17 Oct 2022. It can only be exploited from the same machine or local network, 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-2022-41751 exists.

Affected product: Debian Debian Linux. 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-2022-41751/ (Markdown: https://insights.sbomify.com/CVE-2022-41751/index.md)
```

## Sources

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

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