CVE-2022-41231: Path traversal in Jenkins build-publisher Plugin

org.jenkins-ci.plugins:build-publisher Updated 02 Oct 2025

Summary

22/09/2022

Disclosed on

CVE-2022-41231

CVE

No i

Fix available

Moderate

Severity

5.7

CVSS Score

CVE-2022-41231: Path traversal in Jenkins build-publisher Plugin. Affects org.jenkins-ci.plugins:build-publisher versions < 1.22. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or Browse

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats

SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml

Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile

Javascript package-lock.json · yarn.lock · pnpm-lock.yaml

PHP composer.lock

Python poetry.lock · requirements.txt · Pipfile.lock

Go go.mod

Rust Cargo.lock

Ruby Gemfile.lock

Dart pubspec.lock

C/C++ conan.lock

Elixir mix.lock

Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Background

The Jenkins Build-Publisher Plugin is a Maven package that provides functionality for publishing build artifacts to external repositories. It allows users with Item/Configure permission to configure various settings for publishing builds. This plugin is vulnerable to a path traversal attack, which can lead to unauthorized modification of the config.xml file on the Jenkins controller file system.

Vulnerability Detail

The vulnerability in the Jenkins Build-Publisher Plugin (version 1.22 and earlier) allows attackers with Item/Configure permission to manipulate the config.xml file on the Jenkins controller file system. By providing a crafted file name to an API endpoint, an attacker can create or replace any config.xml file. Additionally, the endpoint does not require POST requests, making it susceptible to cross-site request forgery (CSRF) attacks. This vulnerability enables attackers to replace config.xml files with empty files, potentially disrupting the functionality of the affected Jenkins instance.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

No workaround is currently available for this vulnerability.

Conclusion

The Jenkins Build-Publisher Plugin is vulnerable to a path traversal attack that allows unauthorized modification of config.xml files on the Jenkins controller file system. Currently, there is no known fix or workaround for this vulnerability, and the plugin has been suspended. It is recommended to stay updated with official Jenkins security advisories for any future developments. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.jenkins-ci.plugins:build-publisher →