Autocomplete ParameterApplication · Jenkins
CVE-2022-30969
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 · uneditedA cross-site request forgery (CSRF) vulnerability in Jenkins Autocomplete Parameter Plugin 1.1 and earlier allows attackers to execute arbitrary code without sandbox protection if the victim is an administrator.
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 confidenceA CSRF vulnerability in Jenkins Autocomplete Parameter Plugin 1.1 and earlier allows authenticated administrators to be tricked into executing arbitrary code without sandbox protection. An attacker crafts a malicious request that, when triggered by an admin session, can execute arbitrary code on the Jenkins server.
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
Autocomplete ParameterApplication
<= 1.1CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Verify Autocomplete Parameter Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or check the plugin directory at $JENKINS_HOME/plugins/ for the autocomplete-parameter plugin folderAffected if The plugin is present in the Jenkins instance
-
Determine the installed plugin versionIn Jenkins > Manage Jenkins > Manage Plugins > Installed tab, locate Autocomplete Parameter and note the version number displayedAffected if The version is 1.1 or earlier (any version up to and including 1.1)
-
Check if administrative configuration is accessibleNavigate to Jenkins > Manage Jenkins > Configure System and look for Autocomplete Parameter configuration sections, or check for job parameters using Autocomplete Parameter typeAffected if Administrative configuration UI for the plugin is accessible or the plugin is used in job configurations
-
Confirm admin session handlingReview Jenkins security realm configuration at Jenkins > Manage Jenkins > Configure Global Security to verify how administrator sessions are managedAffected if No additional CSRF tokens or confirmation dialogs are required for plugin configuration changes
If the Autocomplete Parameter Plugin version 1.1 or earlier is installed and accessible to administrators, the environment is affected by this CVE.
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.
dbcve · scopedUpdate Jenkins Autocomplete Parameter Plugin to a patched version. As a compensating control, restrict admin session cookies and implement additional validation for administrative actions.
Upgrade to the latest available version of Autocomplete Parameter plugin (version 1.2 or later)
- 1. In the Jenkins dashboard, navigate to 'Manage Jenkins'
- 2. Click on 'Manage Plugins'
- 3. Go to the 'Installed' tab
- 4. Locate 'Autocomplete Parameter' in the list of installed plugins
- 5. If a newer version is available, select the plugin and click 'Update'
- 6. Restart Jenkins to apply the update
- 7. Alternatively, download the fixed plugin (.hpi) from the Jenkins plugin repository and upload it via 'Advanced Settings' > 'Upload Plugin'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Autocomplete Parameter
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-30969 — 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-30969 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