# CVE-2022-36914: Jenkins Files Found Trigger Plugin allows attackers to check for existence of attacker-specified file path on Jenkins controller file system

> Attackers with read permissions can check for the existence of arbitrary files on the Jenkins controller file system due to missing permission checks.

- **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:** 27 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-jj8j-6jq7-gmvh

## What is CVE-2022-36914?

CVE-2022-36914 is a medium-severity missing authorization vulnerability in Jenkins Files Found Trigger Plugin, published on 27 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Files Found Trigger Plugin 1.5 and earlier does not perform a permission check in a method implementing form validation, allowing attackers with Overall/Read permission to check for the existence of an attacker-specified file path on the Jenkins controller file system.

Weakness: CWE-862 (Missing Authorization)

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

2 open source packages ship an affected version, including org.jenkins-ci.plugins:files-found-trigger. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:files-found-trigger` | Maven | All versions to 1.5 | None |
| `org.jenkins-ci.plugins:files-found-trigger` | Maven | All versions to 1.5 | None |

Products: Jenkins Files Found Trigger.

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

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

## Is CVE-2022-36914 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36914 is a medium-severity missing authorization vulnerability in Jenkins Files Found Trigger Plugin, published on 27 Jul 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-36914 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:files-found-trigger (Maven): affected all versions up to 1.5; no fix listed
- org.jenkins-ci.plugins:files-found-trigger (Maven): affected all versions up to 1.5; 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-36914/ (Markdown: https://insights.sbomify.com/CVE-2022-36914/index.md)
```

## Sources

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

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