# CVE-2022-36231: Code injection in pdf_info

> Attackers can execute arbitrary commands via the pdf_info Ruby library due to unsafe backtick usage.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Feb 2023
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-9fh3-j99m-f4v7

## What is CVE-2022-36231?

CVE-2022-36231 is a critical command injection vulnerability in n/a, published on 23 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

pdf_info 0.5.3 is vulnerable to Command Execution because the Ruby code uses backticks instead of Open3.

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

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

2 open source packages ship an affected version, including pdf_info. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pdf_info` | RubyGems | All versions to 0.5.3 | None |
| `pdf_info` | RubyGems | All versions to 0.5.3 | None |

Products: Newspaperclub Pdf Info.

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

No fix has been published for CVE-2022-36231 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-36231 being exploited?

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

Public exploit code:

- pdf_info <= 0.5.3 OS Command Injection (github_poc): https://github.com/affix/CVE-2022-36231

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36231 is a critical command injection vulnerability in n/a, published on 23 Feb 2023. 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-2022-36231 exists.

Affected packages and fixed versions:
- pdf_info (RubyGems): affected all versions up to 0.5.3; no fix listed
- pdf_info (RubyGems): affected all versions up to 0.5.3; no fix listed

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

## Sources

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

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