Registry traffic interception via disabled certificate validation
Published Apr 12, 2023 · Updated Feb 7, 2025
Improper certificate validation in Jenkins Image Tag Parameter Plugin 2.0 allows remote attackers to intercept Docker registry traffic. The serialized verifySsl field is absent from pre-2.0 job definitions, and the 2.0 upgrade path treats that missing setting as disabled when requesting image tags. A man-in-the-middle position and use of a legacy Image Tag Parameter are required, exposing registry responses and any credentials sent with the request.
Summary
What happened
Improper certificate validation in Jenkins Image Tag Parameter Plugin 2.0 allows remote attackers to intercept Docker registry traffic. The serialized verifySsl field is absent from pre-2.0 job definitions, and the 2.0 upgrade path treats that missing setting as disabled when requesting image tags. A man-in-the-middle position and use of a legacy Image Tag Parameter are required, exposing registry responses and any credentials sent with the request.
The record
- CVE
- CVE-2023-30516
- Published
- Apr 12, 2023
- Updated
- Feb 7, 2025
- Vendor
- Jenkins Project
- Product
- Image Tag Parameter Plugin
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 12, 2023CVE publishedPublication date reported by the CVE source.
- Feb 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo