# CVE-2022-43433: Content-Security-Policy protection for user content disabled by Jenkins ScreenRecorder Plugin

> The Jenkins ScreenRecorder Plugin disables Content-Security-Policy protections for user-generated content, allowing attackers to bypass security controls.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 19 Oct 2022
- **Updated:** 8 May 2025
- **Also known as:** GHSA-cvxj-4745-843x

## What is CVE-2022-43433?

CVE-2022-43433 is a medium-severity vulnerability in Jenkins ScreenRecorder Plugin, published on 19 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins ScreenRecorder Plugin 0.7 and earlier programmatically disables Content-Security-Policy protection for user-generated content in workspaces, archived artifacts, etc. that Jenkins offers for download.

Weakness: CWE-693 (Protection Mechanism Failure)

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

2 open source packages ship an affected version, including io.jenkins.plugins:screenrecorder. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.jenkins.plugins:screenrecorder` | Maven | All versions to 0.7 | None |
| `io.jenkins.plugins:screenrecorder` | Maven | All versions to 0.7 | None |

Products: Jenkins Screenrecorder.

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

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

## Is CVE-2022-43433 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-43433 is a medium-severity vulnerability in Jenkins ScreenRecorder Plugin, published on 19 Oct 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-43433 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.jenkins.plugins:screenrecorder (Maven): affected all versions up to 0.7; no fix listed
- io.jenkins.plugins:screenrecorder (Maven): affected all versions up to 0.7; 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-43433/ (Markdown: https://insights.sbomify.com/CVE-2022-43433/index.md)
```

## Sources

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

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