# CVE-2022-1813: OS Command Injection in yogeshojha/rengine

> Attackers can execute arbitrary OS commands on the server hosting the rengine web application.

- **Severity:** High 8.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-62j3-37pc-h32g

## What is CVE-2022-1813?

CVE-2022-1813 is a high-severity command injection vulnerability in yogeshojha/rengine, published on 22 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OS Command Injection in GitHub repository yogeshojha/rengine prior to 1.2.0.

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

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

It affects 1 product.


Products: Rengine Project Rengine.

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

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

## Is CVE-2022-1813 being exploited?

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

## Other vulnerabilities in yogeshojha/rengine

- [CVE-2021-39491](https://insights.sbomify.com/CVE-2021-39491/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1813 is a high-severity command injection vulnerability in yogeshojha/rengine, published on 22 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1813 in the wild and no public exploit code.

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

## Sources

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

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