Vulnerability in github.com/canonical/pebble (CVE-2024-3250)
Summary
Vulnerability in github.com/canonical/pebble (CVE-2024-3250). Confidential information can be exposed externally. Exploitable via GET /v1/files. Mitigation: upgrade to 1.1.1 or later.
Original description
The description as published by the source.
It was discovered that Canonical's Pebble service manager read-file API and the associated pebble pull command, before v1.10.2, allowed unprivileged local users to read files with root-equivalent permissions when Pebble was running as root. Fixes are also available as backports to v1.1.1, v1.4.2, and v1.7.4.
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-2024-3250 has been found in github.com/canonical/pebble.
Attackers can target a specific entry point like GET /v1/files over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade github.com/canonical/pebble to 1.1.1 or later.
If unsure, ask your IT team or search "github.com/canonical/pebble CVE-2024-3250" on the vendor's site.
CVE-2024-3250 (github.com/canonical/pebble) — CWE-862
Attack vector: local / no user interaction
Attack surface: GET /v1/files
Patched: 1.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 (CWE-862) exists in github.com/canonical/pebble. Attackers reach the vulnerable code path via GET /v1/files.
Check the vendor advisory for the affected versions of github.com/canonical/pebble. Attack surface: GET /v1/files.
Severity: ?. Confidential information can be exposed externally.
Update to 1.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 GET /v1/files requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/canonical/pebble' . 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
-
1Identify exposure identify
grep -r 'github.com/canonical/pebble' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/canonical/pebbleを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /v1/files' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /v1/filesへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/canonical/pebble to 1.1.1ステージング環境で 1.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /v1/files on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- report github.com
- report cve.org
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com