Loading HuntDB...

CVE-2024-3250

MEDIUM
Published 2024-04-04T14:29:31.250Z
Actions:

Expert Analysis

Professional remediation guidance

Get tailored security recommendations from our analyst team for CVE-2024-3250. We'll provide specific mitigation strategies based on your environment and risk profile.

CVSS Score

V3.1
6.5
/10
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Base Score Metrics
Exploitability: N/A Impact: N/A

EPSS Score

v2025.03.14
0.000
probability
of exploitation in the wild

There is a 0.0% chance that this vulnerability will be exploited in the wild within the next 30 days.

Updated: 2025-06-25
Exploit Probability
Percentile: 0.061
Higher than 6.1% of all CVEs

Attack Vector Metrics

Attack Vector
LOCAL
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
CHANGED

Impact Metrics

Confidentiality
HIGH
Integrity
NONE
Availability
NONE

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.

Understanding This Vulnerability

This Common Vulnerabilities and Exposures (CVE) entry provides detailed information about a security vulnerability that has been publicly disclosed. CVEs are standardized identifiers assigned by MITRE Corporation to track and catalog security vulnerabilities across software and hardware products.

The severity rating (MEDIUM) indicates the potential impact of this vulnerability based on the CVSS (Common Vulnerability Scoring System) framework. Higher severity ratings typically indicate vulnerabilities that could lead to more significant security breaches if exploited. Security teams should prioritize remediation efforts based on severity, exploit availability, and the EPSS (Exploit Prediction Scoring System) score, which predicts the likelihood of exploitation in the wild.

If this vulnerability affects products or systems in your infrastructure, we recommend reviewing the affected products section, checking for available patches or updates from vendors, and implementing recommended workarounds or solutions until a permanent fix is available. Organizations should also monitor security advisories and threat intelligence feeds for updates about active exploitation of this vulnerability.

Available Exploits

No exploits available for this CVE.

Related News

No news articles found for this CVE.

Affected Products

References

Credits & Acknowledgments

finder

Harry Pidcock

finder

Ben Hoyt

remediation developer

Ben Hoyt

GitHub Security Advisories

Community-driven vulnerability intelligence from GitHub

✓ GitHub Reviewed MODERATE

Pebble service manager's file pull API allows access by any user

GHSA-4685-2x5r-65pj

Advisory Details

### Impact Note: "Pebble" here refers to [Canonical's service manager](https://github.com/canonical/pebble), not the [Let's Encrypt ACME test server](https://github.com/letsencrypt/pebble). The API behind `pebble pull`, used to read files from the workload container by Juju charms, allows access from any user, instead of just admin. In Juju Kubernetes sidecar charms, Pebble and the charm run as root, so they have full access. But if another restricted unix user gains local access to the container host, they could hit the Pebble `GET /v1/files?action=read` API and would be allowed to read any file in the workload container, for example an ssh key or database password or other sensitive information. If there are ssh keys they could then potentially ssh into the workload, or if something like a database password they could log into the database. Note that this requires local user access to the host machine. It seems unlikely that an attacker could gain this level of access in a Juju Kubernetes context, but if someone did and there's sensitive information in files accessible to Pebble, the consequences are bad. To reproduce the issue, go back to the Pebble version in Juju 2.9 (5842ea68c9c7), do `pebble run` as root in one terminal window, then in another terminal window, as a regular user, use the `pebble pull` CLI. You will be able to pull any file as a regular user. ### Patches The original patch is commit https://github.com/canonical/pebble/commit/cd326225b9b0be067da7d8858e2c912078cbbbd5. There's also https://github.com/canonical/pebble/pull/406, which fixes this issue in more recent Pebble versions (that PR also fixes a separate issue we introduced more recently, but hasn't been released in Juju yet). We released the fix in the following Pebble versions: - https://github.com/canonical/pebble/releases/tag/v1.1.1 - https://github.com/canonical/pebble/releases/tag/v1.4.2 - https://github.com/canonical/pebble/releases/tag/v1.7.4 - https://github.com/canonical/pebble/releases/tag/v1.10.2 Juju will be releasing patch versions with this fix shortly: - Juju 2.9.49 (Pebble v1.1.1) - Juju 3.1.8 (Pebble v1.4.2) - Juju 3.3.4 (Pebble v1.4.2) - Juju 3.4.2 (Pebble v1.7.4) - Juju 3.5.0 (Pebble v1.10.2) ### References * https://www.cve.org/CVERecord?id=CVE-2024-3250

Affected Packages

Go github.com/canonical/pebble
ECOSYSTEM: ≥1.2.0 <1.4.2
Go github.com/canonical/pebble
ECOSYSTEM: ≥1.5.0 <1.7.3
Go github.com/canonical/pebble
ECOSYSTEM: ≥1.8.0 <1.10.2
Go github.com/canonical/pebble
ECOSYSTEM: ≥0 <1.1.1

CVSS Scoring

CVSS Score

5.0

CVSS Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Advisory provided by GitHub Security Advisory Database. Published: April 5, 2024, Modified: April 5, 2024

References

Published: 2024-04-04T14:29:31.250Z
Last Modified: 2024-11-06T15:43:34.482Z
Copied to clipboard!