Security readout for executives and security teams
Plain-English summary
This flaw lets a Jenkins user who already has job configuration rights abuse the Build-Publisher Plugin to create or overwrite Jenkins config.xml files on the controller. That can damage trusted configuration and may support privilege or workflow abuse, but it is not described as unauthenticated or actively exploited in the provided sources.
Executive priority
Treat this as a targeted Jenkins integrity risk, not a broad internet emergency. Prioritize CI/CD environments where many users can configure jobs, because unauthorized controller configuration changes can undermine build trust and delivery controls.
Technical view
CVE-2022-41231 is a path traversal issue in Jenkins Build-Publisher Plugin 1.22 and earlier. An API endpoint accepts a crafted file name, allowing users with Item/Configure permission to create or replace any config.xml file on the Jenkins controller filesystem. CVSS 3.1 score is 5.7, with high integrity impact.
Likely exposure
Exposure is limited to Jenkins environments running Build-Publisher Plugin 1.22 or earlier where users with Item/Configure permission can access the vulnerable API endpoint. The source bundle does not identify affected forks, hosted services, or downstream products.
Exploitation context
The bundle does not cite active exploitation and KEV status is false. Exploitation requires authenticated Jenkins access with Item/Configure permission and user interaction per the CVSS vector. The main risk is unauthorized modification of Jenkins controller configuration, not direct data theft.
Researcher notes
The provided evidence supports CWE-22 path traversal with arbitrary config.xml create or replace on the controller filesystem. The advisory reference is central, but the bundle does not include a fixed version, exploit evidence, or detailed endpoint behavior, so validation should remain non-invasive and permission-focused.
Mitigation direction
- Inventory Jenkins instances for Build-Publisher Plugin 1.22 or earlier.
- Check Jenkins advisory and plugin guidance for available remediation.
- Remove or disable the plugin where it is not operationally required.
- Restrict Item/Configure permission to trusted administrators only.
- Monitor Jenkins controller config.xml changes for unexpected modifications.
Validation and detection
- Confirm whether Build-Publisher Plugin is installed on each Jenkins controller.
- Record the installed plugin version and compare it to 1.22 and earlier.
- Review users and groups granted Item/Configure permission.
- Inspect recent Jenkins configuration changes for unexplained config.xml updates.
- Track vendor guidance before declaring remediation complete.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-41231 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N2.13.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.7MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.jenkins.io/security/advisory/2022-09-21/#SECURITY-2139CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.