Vulnerability in Jenkins Parameterized Trigger Plugin (CVE-2022-27195)

Summary

Vulnerability in Jenkins Parameterized Trigger Plugin (CVE-2022-27195). Confidential information can be exposed externally. Exploitable via build.xml.

Original description

The description as published by the source.

Jenkins Parameterized Trigger Plugin 2.43 and earlier captures environment variables passed to builds triggered using Jenkins Parameterized Trigger Plugin, including password parameter values, in their build.xml files. These values are stored unencrypted and can be viewed by users with access to the Jenkins controller file system.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2022-27195 has been found in Jenkins Parameterized Trigger Plugin.
Attackers can target a specific entry point like build.xml over the network to misuse the product.
Confidential information can be exposed externally.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Jenkins Parameterized Trigger Plugin CVE-2022-27195" on the vendor's site.

CVE-2022-27195 (Jenkins Parameterized Trigger Plugin)
Attack vector: local / no user interaction
Attack surface: build.xml
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in Jenkins Parameterized Trigger Plugin. Attackers reach the vulnerable code path via build.xml.

📍 Affected scope

Check the vendor advisory for the affected versions of Jenkins Parameterized Trigger Plugin. Attack surface: build.xml.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで Jenkins Parameterized Trigger Plugin を使っているサービスとバージョンを洗い出す。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

advisory openwall.com
advisory jenkins.io