Pipeline\Application · Jenkins
CVE-2022-28155
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 Pipeline: Phoenix AutoTest Plugin 1.3 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.
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 contains an XML parser that is not configured to prevent XML External Entity (XXE) attacks. An attacker can craft malicious XML input containing external entity references to potentially read local files, perform Server-Side Request Forgery (SSRF), or cause denial of service.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 Phoenix AutoTest Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed, or run: jenkins-cli.jar who-am-i or check $JENKINS_HOME/plugins for phoenix-autotest directoryAffected if The plugin directory exists in the Jenkins plugins folder or the plugin appears in the installed list
-
Determine installed plugin versionCheck the manifest file: $JENKINS_HOME/plugins/phoenix-autotest/META-INF/MANIFEST.MF for the Bundle-Version attribute, or view the plugin details in the Jenkins plugin manager UIAffected if The version listed is 1.3 or lower (1.3, 1.2, 1.1, 1.0, etc.)
-
Identify pipelines using Phoenix AutoTest functionsSearch job configurations and Jenkinsfiles for references to 'phoenix' or 'autotest' pipeline steps. Use Jenkins script console: Jenkins.instance.allItems.each { job -> if (job.definition?.script?.contains('phoenix') || job.definition?.script?.contains('autotest')) { println job.fullName } }Affected if Any Pipeline jobs or Freestyle projects reference or call Phoenix AutoTest plugin functions
-
Check for XML input processed by the pluginReview the job configurations or pipeline scripts that use the Phoenix AutoTest plugin to see if they accept or process XML input files, test results, or XML-based configurationsAffected if The plugin processes XML input from files, URLs, or build parameters as part of automated testing workflows
You are affected if the Phoenix AutoTest Plugin version 1.3 or earlier is installed AND your pipelines or jobs actively use the plugin to process XML input.
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 Phoenix AutoTest Plugin version 1.4 or later which properly configures the XML parser to prevent XXE attacks. If upgrading is not immediately possible, restrict XML input sources and validate XML content before parsing.
Fix this in Pipeline\
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing4.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,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28155 — 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-28155 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