# CVE-2022-45132: Code injection in n/a

> Remote attackers can execute arbitrary code on the LAVA server by submitting malicious Jinja2 templates via the REST API.

- **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:** Yes
- **Published:** 18 Nov 2022
- **Updated:** 30 Apr 2025
- **Also known as:** DEBIAN-CVE-2022-45132, GHSA-wjxx-hxfj-hfmh

## What is CVE-2022-45132?

CVE-2022-45132 is a critical code injection vulnerability in n/a, published on 18 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Linaro Automated Validation Architecture (LAVA) before 2022.11.1, remote code execution can be achieved through user-submitted Jinja2 template. The REST API endpoint for validating device configuration files in lava-server loads input as a Jinja2 template in a way that can be used to trigger remote code execution in the LAVA server.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Linaro Lava.

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

Upgrade to a fixed version.

## Is CVE-2022-45132 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-12563](https://insights.sbomify.com/CVE-2018-12563/): Path traversal in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45132 is a critical code injection vulnerability in n/a, published on 18 Nov 2022. 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-45132 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-2022-45132/ (Markdown: https://insights.sbomify.com/CVE-2022-45132/index.md)
```

## Sources

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

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