Vulnerability in pcp
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 DEBIAN-CVE-2024-3019 has been found in pcp.
Risk of unauthorized operations or information disclosure.
What to do: upgrade pcp to 6.2.1-1 or later.
If unsure, ask your IT team or search "pcp DEBIAN-CVE-2024-3019" on the vendor's site.
DEBIAN-CVE-2024-3019 (pcp)
Patched: 6.2.1-1 — 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.
A vulnerability (unclassified) exists in pcp.
Check the vendor advisory for the affected versions of pcp.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 6.2.1-1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pcp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'pcp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pcpを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade pcp to 6.2.1-1ステージング環境で 6.2.1-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Package | Affected → Fixed | |
|---|---|---|
| Debian:11pcp |
All versions→ Not listed |
Not listed |
| Debian:12pcp |
All versions→ Not listed |
Not listed |
| Debian:13pcp |
< 6.2.1-1→ 6.2.1-1 |
6.2.1-1 |
| Debian:14pcp |
< 6.2.1-1→ 6.2.1-1 |
6.2.1-1 |
Original description The description as published by the source.
A flaw was found in PCP. The default pmproxy configuration exposes the Redis server backend to the local network, allowing remote command execution with the privileges of the Redis user. This issue can only be exploited when pmproxy is running. By default, pmproxy is not running and needs to be started manually. The pmproxy service is usually started from the 'Metrics settings' page of the Cockpit web interface. This flaw affects PCP versions 4.3.4 and newer.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory security-tracker.debian.org