HIGH CVSS 8.0
Published: 2022-09-21

CVE-2022-41232

jenkins build-publisher Security Advisory (CVE-2022-41232)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2022-41232?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2022-41232 impacting jenkins build-publisher. Evaluated with CVSS Base Score of 8.0 (HIGH).

Original NVD Description

Source: NIST NVD
A cross-site request forgery (CSRF) vulnerability in Jenkins Build-Publisher Plugin 1.22 and earlier allows attackers to replace any config.xml file on the Jenkins controller file system with an empty file by providing a crafted file name to an API endpoint.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
Low (AC:L)
No specialized conditions required
Privileges Required
Low (PR:L)
Standard user access required
User Interaction
Required (UI:R)
User must click or open resource
Scope
Unchanged (S:U)
Confined to same security context
Confidentiality
High (C:H)
Total information disclosure
Integrity
High (I:H)
Total modification of target system
Availability
High (A:H)
Total denial of service or shutdown

🎯 Affected Versions Matrix

Affected Product jenkins / build-publisher
Affected Versions *
Weakness Enumeration CWE-352

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2022-41232 impacting jenkins build-publisher.

⚡ Nuclei Detection Template (YAML) cve-2022-41232.yaml
id: cve-2022-41232

info:
  name: jenkins build-publisher - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: high
  description: |
    Automated signature & scanner for CVE-2022-41232 affecting jenkins build-publisher.
    Evaluation: A cross-site request forgery (CSRF) vulnerability in Jenkins Build-Publisher Plugin 1.22 and earlier allows attackers to replace any config.xml file o...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2022-41232
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
    cvss-score: 8.0
    cve-id: CVE-2022-41232
    cwe-id: CWE-352
  tags: cve,cve-2022-41232,jenkins,build-publisher,high

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "build-publisher"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2022-41232.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2022-41232
# Target: jenkins build-publisher | CVSS: 8.0 (HIGH)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2022-41232 (jenkins build-publisher)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against jenkins build-publisher scope (*).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2022-41232.sh
# Recommended Remediation & Patching Commands for CVE-2022-41232
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install build-publisher 2>/dev/null || \
sudo dnf upgrade build-publisher 2>/dev/null || \
sudo yum update build-publisher

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i build-publisher 2>/dev/null || rpm -qa | grep -i build-publisher

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

🔗 Verified Technical References

Authorities
  • No records filed in this category.
Distributions
  • No records filed in this category.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2022-41232 in jenkins build-publisher?

Review vendor-specific security notices and update jenkins build-publisher packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2022-41232?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2022-41232?

CVE-2022-41232 is classified with a CVSS 3.1 Base Score of 8.0 (HIGH). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
8.0
HIGH SEVERITY
CVE ID CVE-2022-41232
Weakness CWE-352
Vendor jenkins
Product build-publisher
Published 2022-09-21
Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H