What is the severity of CVE-2022-45400?

CVE-2022-45400 is rated as a high severity vulnerability due to its potential for XML external entity (XXE) attacks.

How do I fix CVE-2022-45400?

To fix CVE-2022-45400, upgrade the Jenkins JAPEX Plugin to version 1.8 or later.

What type of attacks does CVE-2022-45400 make possible?

CVE-2022-45400 makes it possible for attackers to exploit XML external entity (XXE) vulnerabilities.

Which versions of the Jenkins JAPEX Plugin are affected by CVE-2022-45400?

Versions of the Jenkins JAPEX Plugin up to and including 1.7 are affected by CVE-2022-45400.

Is there any workaround for CVE-2022-45400?

There are no known workarounds for CVE-2022-45400; the only solution is to update to a secure version.

Vulnerability/
CVE-2022-45400

critical

9.8

CWE

611

15/11/2022

16/11/2022

30/4/2025

CVE-2022-45400: XEE

First published: Tue Nov 15 2022(Updated: )

JAPEX Plugin 1.7 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks. This allows attackers able to control XML input files for the 'Record Japex test report' post-build step to have Jenkins parse a crafted file that uses external entities for extraction of secrets from the Jenkins controller or server-side request forgery.

Credit: jenkinsci-cert@googlegroups.com

Affected Software	Affected Version	How to fix
Jenkins	<=1.7
maven/org.jvnet.hudson.plugins:japex	<=1.7

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-45400?
CVE-2022-45400 is rated as a high severity vulnerability due to its potential for XML external entity (XXE) attacks.
How do I fix CVE-2022-45400?
To fix CVE-2022-45400, upgrade the Jenkins JAPEX Plugin to version 1.8 or later.
What type of attacks does CVE-2022-45400 make possible?
CVE-2022-45400 makes it possible for attackers to exploit XML external entity (XXE) vulnerabilities.
Which versions of the Jenkins JAPEX Plugin are affected by CVE-2022-45400?
Versions of the Jenkins JAPEX Plugin up to and including 1.7 are affected by CVE-2022-45400.
Is there any workaround for CVE-2022-45400?
There are no known workarounds for CVE-2022-45400; the only solution is to update to a secure version.

agent/type
agent/weakness
agent/first-publish-date
collector/nvd-index
agent/software-canonical-lookup-request
agent/author
collector/mitre-cve
source/MITRE
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/last-modified-date
agent/references
agent/severity
collector/github-advisory-latest
source/GitHub
alias/GHSA-8538-25v4-25pg
alias/CVE-2022-45400
agent/source
agent/description
collector/nvd-cve
agent/softwarecombine
agent/tags
agent/event
collector/github-advisory
vendor/jenkins
canonical/jenkins
version/jenkins/1.7
package-manager/maven

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.