Pipeline\Application · Jenkins
CVE-2022-28158
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 · uneditedA missing permission check in Jenkins Pipeline: Phoenix AutoTest Plugin 1.3 and earlier allows attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.
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 Pipeline: Phoenix AutoTest Plugin versions 1.3 and earlier lacks proper permission validation in certain API endpoints. An attacker with basic Overall/Read permission can enumerate credential IDs stored in Jenkins' credential store by making specially crafted API calls. While this does not directly expose credential secrets, it reveals credential identifiers that can aid in targeted attacks.
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
Pipeline\Application
<= 1.3CVSS 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 Pipeline: Phoenix AutoTest Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i 'phoenix autotest'Affected if The plugin appears in the installed plugins list
-
Determine installed plugin versionIn the Installed plugins tab, find the 'Pipeline: Phoenix AutoTest' entry and note the version number displayed in the Version columnAffected if Version is 1.3 or earlier (e.g., 1.3, 1.2, 1.1, 1.0)
-
Confirm Overall/Read permission is activeNavigate to Manage Jenkins > Manage Users > select a user, or check Manage Jenkins > Configure Global Security > Authorization section. Verify that Overall/Read permission is granted to users or anonymous usersAffected if Overall/Read permission is granted to any user group or anonymous access is enabled
-
Check for configured credentialsNavigate to Credentials > System > Domain > (any domain) to see if credentials are stored in Jenkins' credential storeAffected if Any credentials are present in the Jenkins credential store
You are affected if the Pipeline: Phoenix AutoTest Plugin version 1.3 or earlier is installed, Overall/Read permission is enabled, and credentials exist in Jenkins.
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 dataUpdate to a patched version of the Pipeline: Phoenix AutoTest Plugin. If no patched version is available, audit and restrict Overall/Read permissions to trusted users only, and review credential usage in any Jenkins pipelines using this plugin.
Fix this in Pipeline\
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28158 — 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-28158 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