CVE-2023-30529 json
Jenkins Lucene-Search Plugin vulnerable to Cross-Site Request Forgery
published 2023-04-12 3 y ago modified 2026-06-17 4 mo ago also GHSA-gh5w-gffh-68pr , EUVD-2023-1308
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
Jenkins Lucene-Search Plugin 387.v938a_ecb_f7fe9 and earlier does not require POST requests for an HTTP endpoint, allowing attackers to reindex the database.
Patch / fix
- maven org.jenkins-ci.plugins:lucene-search 398.v3dfa_cb_223984
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 21 mo ago
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:lucene-search | <398.v3dfa_cb_223984 |
398.v3dfa_cb_223984 |
Affected products
- Jenkins Project Jenkins Lucene-Search Plugin
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/jenkinsci/lucene-search-plugin/commit/828f79fedbe3da08b17937a85b98b5d7f499a8dd
web
-
github.com
/jenkinsci/lucene-search-plugin/commit/ffd691642b8dda63b55cfc7e73993336554dbcb2
web
-
jenkins.io
/security/advisory/2023-04-12/#SECURITY-3013
vendor-advisory, web
-
openwall.com
/lists/oss-security/2023/04/13/3
web, mailing-list, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-30529
advisory
Sources
- CVE List CVE-2023-30529
- GitHub Advisory GHSA-gh5w-gffh-68pr
- NVD CVE-2023-30529
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.