# CVE-2022-36910: Lucene-Search Plugin does not perform permission checks in several HTTP endpoints

> Attackers with read permissions can reindex the database and access job information they should not see due to missing permission checks.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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:** Yes
- **Published:** 27 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-m8w5-vwq3-gp8f

## What is CVE-2022-36910?

CVE-2022-36910 is a medium-severity missing authorization vulnerability in Jenkins Lucene-Search 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 Lucene-Search Plugin 370.v62a5f618cd3a and earlier does not perform a permission check in several HTTP endpoints, allowing attackers with Overall/Read permission to reindex the database and to obtain information about jobs otherwise inaccessible to them.

Weakness: CWE-862 (Missing Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:lucene-search` | Maven | All versions | 387.v938a |
| `org.jenkins-ci.plugins:lucene-search` | Maven | All versions | 387.v938a |

Products: Jenkins Lucene-Search.

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

Upgrade org.jenkins-ci.plugins:lucene-search to 387.v938a or later.

## Is CVE-2022-36910 being exploited?

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

## Other vulnerabilities in Jenkins Lucene-Search Plugin

- [CVE-2022-36922](https://insights.sbomify.com/CVE-2022-36922/): Jenkins Lucene-Search Plugin vulnerable to reflected (XSS) cross-site scripting (medium 6.1)
- [CVE-2023-30529](https://insights.sbomify.com/CVE-2023-30529/): Jenkins Lucene-Search Plugin vulnerable to Cross-Site Request Forgery (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36910 is a medium-severity missing authorization vulnerability in Jenkins Lucene-Search 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-36910 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:lucene-search (Maven): affected all versions; fixed in 387.v938a
- org.jenkins-ci.plugins:lucene-search (Maven): affected all versions; fixed in 387.v938a

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-36910/ (Markdown: https://insights.sbomify.com/CVE-2022-36910/index.md)
```

## Sources

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

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