dbcve.org
Xp DevApplication · Jenkins

CVE-2022-45389

MEDIUM · 5.3 CVSS v3.1 Published 2022-11-15
Fix available
A fix is available. Upgrade to after 1.0 or later.
See remediation →
62/100
Remediation priority · Elevated
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
A missing permission check in Jenkins XP-Dev Plugin 1.0 and earlier allows unauthenticated attackers to trigger builds of jobs corresponding to an attacker-specified repository.

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 XP-Dev Jenkins Plugin versions 1.0 and earlier lacks authorization checks in its build trigger endpoint, allowing any unauthenticated user to invoke builds for attacker-specified repository jobs. This is a classic broken access control vulnerability where the plugin assumes requests are already authenticated by Jenkins but never verifies permissions itself.

MitigationUpgrade to XP-Dev Plugin version 1.1 or later which implements proper permission checks. If upgrading is not immediately possible, consider restricting network access to the Jenkins instance or disabling the plugin if not required.

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
Xp DevApplication
Affected:<= 1.0

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checks

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

  1. Locate the XP-Dev plugin installation
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or inspect the $JENKINS_HOME/plugins/ directory for a folder named 'xp-dev' or similar. The plugin files typically include a .jpi or .hpi file.
    Affected if The XP-Dev plugin folder or file exists in the plugins directory or appears in the installed plugins list.
  2. Check the installed XP-Dev plugin version
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and locate XP-Dev to view its version. Alternatively, inspect the plugin's manifest file (MANIFEST.MF) inside the xp-dev.jpi or .hpi archive located in $JENKINS_HOME/plugins/.
    Affected if The version listed is 1.0 or earlier (e.g., 1.0, 0.9, or no version shown which defaults to early release).
  3. Identify the build trigger endpoint accessibility
    Examine Jenkins job configurations that use the XP-Dev plugin. Look for a build trigger option labeled 'XP-Dev' or 'XP-Dev Repository Trigger' in the job configuration page. Note whether this trigger is enabled on any jobs.
    Affected if The XP-Dev build trigger is enabled on one or more Jenkins jobs.
  4. Verify if anonymous users can access the trigger URL
    Attempt to access the XP-Dev trigger endpoint directly without authentication. The typical endpoint pattern is /xp-dev/build?job=JOBNAME or similar. Use a stateless HTTP request tool (curl) from an unauthenticated context to test if the endpoint responds without returning an authentication or authorization error.
    Affected if The endpoint returns a successful response or initiates a build without requiring Jenkins authentication credentials.

A user is affected if the XP-Dev plugin version is 1.0 or earlier AND the plugin's build trigger is enabled on any job AND the trigger endpoint accepts requests without authentication.

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.0
Interim mitigation

Upgrade to XP-Dev Plugin version 1.1 or later which implements proper permission checks. If upgrading is not immediately possible, consider restricting network access to the Jenkins instance or disabling the plugin if not required.

Fix this in Xp Dev Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45389 — 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-45389 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