# CVE-2022-4643: docconv pdf_ocr.go ConvertPDFImages os command injection

> Remote attackers can execute arbitrary OS commands via the ConvertPDFImages function in the docconv library.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **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:** 21 Dec 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-6m4h-hfpp-x8cx, GO-2022-1184

## What is CVE-2022-4643?

CVE-2022-4643 is a medium-severity command injection vulnerability in docconv, published on 21 Dec 2022. 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

A vulnerability was found in docconv up to 1.2.0. It has been declared as critical. This vulnerability affects the function ConvertPDFImages of the file pdf_ocr.go. The manipulation of the argument path leads to os command injection. The attack can be initiated remotely. Upgrading to version 1.2.1 is able to address this issue. The name of the patch is b19021ade3d0b71c89d35cb00eb9e589a121faa5. It is recommended to upgrade the affected component. VDB-216502 is the identifier assigned to this vulnerability.

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

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

5 open source packages ship an affected version, including code.sajari.com/docconv and github.com/sajari/docconv. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `code.sajari.com/docconv` | Go | From 1.1.0 | 1.3.5 |
| `code.sajari.com/docconv` | Go | From 1.1.0 | 1.3.5 |
| `code.sajari.com/docconv` | Go | From 1.1.0 | 1.3.5 |
| `github.com/sajari/docconv` | Go | All versions | 1.2.1 |
| `github.com/sajari/docconv` | Go | All versions | 1.2.1 |

Products: Search Docconv.

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

Upgrade code.sajari.com/docconv to 1.3.5 or later.

## Is CVE-2022-4643 being exploited?

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

## Other vulnerabilities in docconv

- [CVE-2022-4741](https://insights.sbomify.com/CVE-2022-4741/): docconv XMLToText memory allocation (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4643 is a medium-severity command injection vulnerability in docconv, published on 21 Dec 2022. 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-2022-4643 in the wild and no public exploit code.

Affected packages and fixed versions:
- code.sajari.com/docconv (Go): affected from 1.1.0; fixed in 1.3.5
- code.sajari.com/docconv (Go): affected from 1.1.0; fixed in 1.3.5
- code.sajari.com/docconv (Go): affected from 1.1.0; fixed in 1.3.5
- github.com/sajari/docconv (Go): affected all versions; fixed in 1.2.1
- github.com/sajari/docconv (Go): affected all versions; fixed in 1.2.1

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

## Sources

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

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