Image Tag ParameterApplication · Jenkins
CVE-2023-30516
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 Image Tag Parameter Plugin 2.0 improperly introduces an option to opt out of SSL/TLS certificate validation when connecting to Docker registries, resulting in job configurations using Image Tag Parameters that were created before 2.0 having SSL/TLS certificate validation disabled by default.
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 · moderate confidenceThe Jenkins Image Tag Parameter Plugin version 2.0 introduced a new option allowing users to disable SSL/TLS certificate validation when connecting to Docker registries. Due to backward compatibility handling, job configurations that existed before upgrading to version 2.0 automatically have SSL/TLS certificate validation disabled by default, creating a potential man-in-the-middle vulnerability.
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
Image Tag ParameterApplication
< 2.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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.
-
Identify installed Image Tag Parameter Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab, or use Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i image-tag-parameterAffected if Plugin version is 2.0 or higher AND there are existing job configurations that were created before the upgrade to 2.0
-
Find jobs using Image Tag ParameterSearch job configurations for the 'imageTagParameter' descriptor or look for the 'Image Tag Parameter' build parameter type in job config.xml files in $JENKINS_HOME/jobs/Affected if Jobs using the Image Tag Parameter plugin exist in the Jenkins instance
-
Check SSL/TLS certificate validation settingExamine job config.xml files for the <sslVerificationDisabled>true</sslVerificationDisabled> element within the imageTagParameter configuration blockAffected if The sslVerificationDisabled element is present and set to true, indicating SSL/TLS validation is disabled for Docker registry connections
-
Review Docker registry endpoint configurationsInspect the <registryUrl> and <registryCredentialsId> fields in affected job configurations to identify which Docker registries are configuredAffected if Jobs connect to Docker registries without SSL/TLS certificate verification enabled
A user is affected if the Image Tag Parameter Plugin version 2.0 or higher is in use with job configurations that existed prior to the upgrade, and those jobs have SSL/TLS certificate validation explicitly disabled for Docker registry connections.
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 data2.0
Upgrade to the fixed version of the Image Tag Parameter Plugin and audit all affected job configurations to re-enable SSL/TLS certificate validation for Docker registry connections.
Fix this in Image Tag Parameter
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30516 — 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-2023-30516 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