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.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
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
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 | 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 include 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.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2022-36914 being exploited?
There is no known exploitation of CVE-2022-36914 in the wild and no public exploit code.
Sources
Also known as GHSA-jj8j-6jq7-gmvh.