ProxmoxApplication · Jenkins
CVE-2022-28144
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.7.0 and earlier does not perform a permission check in several HTTP endpoints, allowing attackers with Overall/Read permission to connect to an attacker-specified host using attacker-specified username and password (perform a connection test), disable SSL/TLS validation for the entire Jenkins controller JVM as part of the connection test (see CVE-2022-28142), and test a rollback with attacker-specified parameters.
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 0.7.0 and earlier lacks permission checks on multiple HTTP endpoints, allowing any user with Overall/Read permission (the lowest Jenkins privilege) to connect to arbitrary hosts with attacker-specified credentials, disable SSL/TLS validation system-wide for the entire JVM, and trigger rollback tests with custom parameters.
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.7.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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Proxmox plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or inspect the JENKINS_HOME/plugins directory for a proxmox folderAffected if The Proxmox plugin appears in the installed plugins list
-
Determine the installed Proxmox plugin versionIn Jenkins > Manage Jenkins > Manage Plugins > Installed tab, find the Proxmox Plugin entry and note the Version column. Alternatively, read the manifest file META-INF/MANIFEST.MF inside the proxmox plugin hpi fileAffected if The version is 0.7.0 or any version lower than 0.7.0
-
Confirm Overall/Read permission is granted to usersNavigate to Jenkins > Manage Jenkins > Manage Users and check user accounts. In Jenkins > Manage Jenkins > Configure Global Security, verify if Overall/Read permission is granted to authenticated users or specific user groupsAffected if Any user account has Overall/Read permission enabled, which is the default for authenticated users in many setups
-
Check if Proxmox plugin features are in useLook for Proxmox-related jobs, configurations in Manage Jenkins > Configure System for Proxmox settings, or inspect job configurations for proxmox template usageAffected if The Proxmox plugin is actively configured or used in any Jenkins jobs
If the Proxmox plugin is installed at version 0.7.0 or earlier and any user has Overall/Read permission, the environment is affected by this vulnerability.
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 to a patched version of the Proxmox Plugin that implements proper permission checks on all HTTP endpoints. If no upgrade is available, disable the Proxmox Plugin entirely or severely restrict who has Overall/Read access.
Fix this in Proxmox
Scoped from the published advisory
- Consultation2.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28144 — 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-28144 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