CVE-2024-3250
MEDIUMCVE-2024-3250 is a medium-severity (CVSS 6.5) CWE-732 vulnerability in github.com/canonical/pebble. O3 Security confirms whether CVE-2024-3250 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Pebble service manager's file pull API allows access by any user
Real-World Exposure
github.com/canonical/pebble🐹github.com/canonical/pebble🐹github.com/canonical/pebble🐹github.com/canonical/pebbleReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/canonical/pebble | ≥ 1.2.0&&< 1.4.2 | 1.4.2 |
| 🐹Go | github.com/canonical/pebble | ≥ 1.5.0&&< 1.7.3 | 1.7.3 |
| 🐹Go | github.com/canonical/pebble | ≥ 1.8.0&&< 1.10.2 | 1.10.2 |
| 🐹Go | github.com/canonical/pebble | all versions | 1.1.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/canonical/pebble. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/canonical/pebble to 1.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-3250 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2024-3250 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2024-3250. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-3250 in your dependencies?
O3 detects CVE-2024-3250 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.