Vulnerability in Jenkins Embeddable Build Status Plugin (CVE-2022-34179)

Summary

Vulnerability in Jenkins Embeddable Build Status Plugin (CVE-2022-34179). Confidential information can be exposed externally. Exploitable via style.

Original description

The description as published by the source.

Jenkins Embeddable Build Status Plugin 2.0.3 and earlier allows specifying a style query parameter that is used to choose a different SVG image style without restricting possible values, resulting in a relative path traversal vulnerability that allows attackers without Overall/Read permission to specify paths to other SVG images on 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-34179 has been found in Jenkins Embeddable Build Status Plugin.
Attackers can target a specific entry point like style 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 Embeddable Build Status Plugin CVE-2022-34179" on the vendor's site.

CVE-2022-34179 (Jenkins Embeddable Build Status Plugin)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: style
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 Embeddable Build Status Plugin. Attackers reach the vulnerable code path via style without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Jenkins Embeddable Build Status Plugin. Attack surface: style.

🔥 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 Embeddable Build Status Plugin を使っているサービスとバージョンを洗い出す。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

advisory jenkins.io