ProxmoxApplication · Jenkins
CVE-2022-28141
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 Proxmox Plugin 0.5.0 and earlier stores the Proxmox Datacenter password unencrypted in the global config.xml file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.
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 Proxmox Plugin versions 0.5.0 and earlier stores the Proxmox Datacenter password in plaintext within the global config.xml file on the Jenkins controller. Any user with filesystem-level access to the Jenkins server can read this file and obtain the plaintext password, resulting in credential disclosure.
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
<= 0.5.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Verify the Proxmox Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Proxmox', or inspect the plugin directory (typically $JENKINS_HOME/plugins/) for a proxmox plugin folder.Affected if The Proxmox Plugin is present in the Jenkins installation.
-
Determine the installed Proxmox Plugin versionIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab, find Proxmox, and note the version shown. Alternatively, check the version file inside the plugin directory (e.g., $JENKINS_HOME/plugins/proxmox/META-INF/MANIFEST.MF).Affected if The version is 0.5.0 or earlier.
-
Locate the Jenkins global configuration fileThe global config.xml file is typically found at $JENKINS_HOME/config.xml. Ensure you have filesystem access to the Jenkins controller.Affected if The config.xml file exists in the Jenkins home directory.
-
Inspect the config.xml for Proxmox password storageOpen $JENKINS_HOME/config.xml in a text editor or use a command like 'grep -i proxmox config.xml' to locate Proxmox-related configuration sections. Look for a <password> or <proxmoxPassword> element containing a plaintext value.Affected if A <password> field under Proxmox configuration contains an actual plaintext password string rather than an encrypted reference.
You are affected if the Proxmox Plugin version is 0.5.0 or earlier AND the global config.xml contains a plaintext password in the Proxmox Datacenter configuration section.
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 Jenkins Proxmox Plugin to a version that encrypts stored credentials, and rotate the exposed Proxmox Datacenter password as a precautionary measure.
Fix this in Proxmox
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28141 — 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-28141 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