dbcve.org
ProxmoxApplication · Jenkins

CVE-2022-28142

HIGH · 7.5 CVSS v3.1 Published 2022-03-29
Fix available
A fix is available. Upgrade to after 0.6.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Jenkins Proxmox Plugin 0.6.0 and earlier disables SSL/TLS certificate validation globally for the Jenkins controller JVM when configured to ignore SSL/TLS issues.

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 confidence

The Jenkins Proxmox Plugin versions 0.6.0 and earlier contain a critical misconfiguration where enabling the option to ignore SSL/TLS certificate validation issues for Proxmox connections instead disables SSL/TLS certificate validation globally across the entire Jenkins controller JVM, affecting all other plugins and outbound SSL/TLS connections.

MitigationUpgrade the Proxmox Plugin to a version after 0.6.0 where this issue is fixed, and avoid using the 'ignore SSL/TLS issues' configuration option until patched. Audit all SSL/TLS connections from the Jenkins controller for potential compromise.

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
ProxmoxApplication
Affected:<= 0.6.0

CVSS 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
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Proxmox plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Proxmox' to view the installed version, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i proxmox
    Affected if The version listed is 0.6.0 or lower
  2. Locate Proxmox plugin configuration
    Navigate to Manage Jenkins > Configure System > look for the Proxmox section (typically under 'Cloud' or 'Proxmox Plugin' settings). The exact path varies by Jenkins version but is generally found in the global configuration area.
    Affected if Configuration section exists and is accessible
  3. Check SSL/TLS validation setting
    Within the Proxmox plugin configuration screen, locate the option related to SSL/TLS certificate validation. Look for settings labeled 'Ignore SSL/TLS issues', 'Disable SSL verification', 'Skip certificate validation', or similar wording that controls SSL/TLS certificate checking.
    Affected if The option to ignore or skip SSL/TLS certificate validation is enabled or checked

You are affected if the Proxmox plugin version is 0.6.0 or earlier AND the option to ignore SSL/TLS certificate validation issues is enabled in the plugin configuration, as this setting disables SSL/TLS validation globally across the Jenkins controller.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 0.6.0
Interim mitigation

Upgrade the Proxmox Plugin to a version after 0.6.0 where this issue is fixed, and avoid using the 'ignore SSL/TLS issues' configuration option until patched. Audit all SSL/TLS connections from the Jenkins controller for potential compromise.

Recommended fix Moderate confidence

Proxmox Plugin 0.6.1 or later

  1. In Jenkins, go to Manage Jenkins > Manage Plugins
  2. Navigate to the 'Installed' tab
  3. Find the Proxmox Plugin in the list
  4. If an update is available, select the plugin and click 'Download now and install after restart'
  5. Wait for the plugin to update and Jenkins to restart
  6. After updating, verify that SSL/TLS certificate validation is properly enforced in the plugin configuration
  7. Do not enable any option that disables SSL/TLS certificate validation
Caveat Review release notes for any configuration changes between your current version and the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Proxmox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28142 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-28142 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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