dbcve.org
JapexApplication · Jenkins

CVE-2022-45400

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-15
Fix available
A fix is available. Upgrade to after 1.7 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Jenkins JAPEX Plugin 1.7 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 confidence

The Jenkins JAPEX Plugin versions 1.7 and earlier contains an XML parser that is not configured to prevent XML External Entity (XXE) attacks. This allows attackers to inject malicious external entity references into XML input processed by the plugin, potentially enabling disclosure of local files, denial of service, or server-side request forgery.

MitigationUpgrade the JAPEX plugin to version 1.8 or later, which properly configures the XML parser to disable external entity processing and prevent XXE 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
JapexApplication
Affected:<= 1.7

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if JAPEX plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'JAPEX' or 'Japex' to see if the plugin is present.
    Affected if JAPEX plugin appears in the installed plugins list
  2. Identify installed JAPEX plugin version
    In the Installed plugins tab, locate the JAPEX plugin and note the version number displayed in the 'Version' column.
    Affected if The version is 1.7 or earlier (e.g., 1.7, 1.6, 1.5, etc.)
  3. Verify XML input processing is in use
    Check if any Jenkins jobs or configurations reference or process JAPEX-related XML files, or look for JAPEX build steps in job configurations.
    Affected if JAPEX XML configuration files are being processed by the plugin
  4. Confirm XML parser vulnerability exists
    Review the plugin's XML parsing implementation if accessible; the vulnerability exists when external entity processing is enabled in the parser configuration.
    Affected if The XML parser used by JAPEX allows external entity resolution (XXE-enabled parser)

If the JAPEX plugin is installed at version 1.7 or earlier and processes XML input, the environment is affected by this XXE vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.7
Interim mitigation

Upgrade the JAPEX plugin to version 1.8 or later, which properly configures the XML parser to disable external entity processing and prevent XXE attacks.

Fix this in Japex Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45400 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-45400 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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