Lucene SearchApplication · Jenkins
CVE-2022-36910
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins Lucene-Search Plugin versions 370.v62a_f618cd3a and earlier lacks proper permission checks on multiple HTTP endpoints. Attackers with only Overall/Read permission (the lowest privilege level) can trigger database reindexing and access information about jobs they should not have access to.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Lucene SearchApplication
<= 370.v62a5f618cd3aCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Lucene-Search plugin is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, or query the REST API at /pluginManager/plugin/lucene-search/api/json to verify the plugin is presentAffected if The plugin is installed and listed in the Jenkins plugin manager
-
Identify the installed version of Lucene-Search pluginView the plugin details in Manage Jenkins > Manage Plugins > Installed, or retrieve via the API at /pluginManager/plugin/lucene-search/api/json - the version is listed in the responseAffected if The displayed version matches 370.v62a5f618cd3a or earlier
-
Compare version against the affected rangeCheck if the installed version is 370.v62a5f618cd3a or any version number lower than this (e.g., 360.v4b_d4e96d0ddfa, 350.v9e8b_7dba_5c2a)Affected if The installed version is 370.v62a5f618cd3a or lower
-
Verify if low-privilege users exist with Overall/Read permissionGo to Manage Jenkins > Manage Users, or check authorization configuration at /configureSecurity/ to see which users or groups have Overall/Read permissionAffected if Any user account exists with Overall/Read permission in the system
-
Confirm vulnerable endpoints are reachableTest access to the Lucene-Search plugin endpoints: /lucene-search/reindex (triggers reindexing) and /lucene-search/search (searches job data) using an account with only Overall/Read permissionAffected if A user with only Overall/Read permission can successfully access these endpoints and trigger actions
The environment is affected if the Lucene-Search plugin version is 370.v62a5f618cd3a or earlier AND there are users with Overall/Read permission who can access the vulnerable endpoints.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade the Lucene-Search Plugin to the latest version that includes the permission check fix.
Fix this in Lucene Search
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36910 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36910 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data