Vulnerability in Jenkins project Jenkins AWS CodeBuild Plugi… (CVE-2018-1000404)

Summary

Vulnerability in Jenkins project Jenkins AWS CodeBuild Plugin (CVE-2018-1000404). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.27 or later.

Original description

The description as published by the source.

Jenkins project Jenkins AWS CodeBuild Plugin version 0.26 and earlier contains a Insufficiently Protected Credentials vulnerability in AWSClientFactory.java, CodeBuilder.java that can result in Credentials Disclosure. This attack appear to be exploitable via local file access. This vulnerability appears to have been fixed in 0.27 and later.

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-2018-1000404 has been found in Jenkins project Jenkins AWS CodeBuild Plugin.
Successful exploitation can lead to full system takeover.
What to do: upgrade Jenkins project Jenkins AWS CodeBuild Plugin to 0.27 or later.
If unsure, ask your IT team or search "Jenkins project Jenkins AWS CodeBuild Plugin CVE-2018-1000404" on the vendor's site.

CVE-2018-1000404 (Jenkins project Jenkins AWS CodeBuild Plugin)
Attack vector: local / no user interaction
Patched: 0.27 — apply immediately
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 project Jenkins AWS CodeBuild Plugin.

📍 Affected scope

Check the vendor advisory for the affected versions of Jenkins project Jenkins AWS CodeBuild Plugin.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 0.27.

🛡️ 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 project Jenkins AWS CodeBuild Plugin を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade Jenkins project Jenkins AWS CodeBuild Plugin to 0.27
```
ステージング環境で 0.27 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

advisory jenkins.io