What is CVE-2024-3250?

CVE-2024-3250 is a medium-severity missing authorization vulnerability in github.com/canonical/pebble (go), affecting versions >= 1.2.0, < 1.4.1. It is fixed in 1.4.2, 1.7.3, 1.10.2, 1.1.1. The application does not perform an authorization check before performing a sensitive operation.

How severe is CVE-2024-3250?

CVE-2024-3250 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/canonical/pebble are affected by CVE-2024-3250?

github.com/canonical/pebble (go) versions >= 1.2.0, < 1.4.1 is affected.

Is there a fix for CVE-2024-3250?

Yes. CVE-2024-3250 is fixed in 1.4.2, 1.7.3, 1.10.2, 1.1.1. Upgrade to this version or later.

Is CVE-2024-3250 exploitable, and should I be worried?

Whether CVE-2024-3250 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-3250 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-3250?

Upgrade: github.com/canonical/pebble to 1.4.2 or later, github.com/canonical/pebble to 1.7.3 or later, github.com/canonical/pebble to 1.10.2 or later, github.com/canonical/pebble to 1.1.1 or later.

CVE-2024-3250 in github.com/canonical/pebble

Q: How severe is CVE-2024-3250?

CVE-2024-3250 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/canonical/pebble are affected by CVE-2024-3250?

github.com/canonical/pebble (go) versions >= 1.2.0, < 1.4.1 is affected.

Q: Is there a fix for CVE-2024-3250?

Yes. CVE-2024-3250 is fixed in 1.4.2, 1.7.3, 1.10.2, 1.1.1. Upgrade to this version or later.

Q: Is CVE-2024-3250 exploitable, and should I be worried?

Whether CVE-2024-3250 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-3250 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-3250?

Upgrade: github.com/canonical/pebble to 1.4.2 or later, github.com/canonical/pebble to 1.7.3 or later, github.com/canonical/pebble to 1.10.2 or later, github.com/canonical/pebble to 1.1.1 or later.

Summary

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

References

https://www.cve.org/CVERecord?id=CVE-2024-3250

Impact

Note: "Pebble" here refers to Canonical's service manager, not the Let's Encrypt ACME test server.

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.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2024-3250 has a CVSS score of 6.5 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.4.2, 1.7.3, 1.10.2, 1.1.1); upgrading removes the vulnerable code path.

Affected versions

github.com/canonical/pebble (>= 1.2.0, < 1.4.1) github.com/canonical/pebble (>= 1.5.0, < 1.7.3) github.com/canonical/pebble (>= 1.8.0, < 1.10.1) github.com/canonical/pebble (< 1.1.1)

Security releases

github.com/canonical/pebble → 1.4.2 (go) github.com/canonical/pebble → 1.7.3 (go) github.com/canonical/pebble → 1.10.2 (go) github.com/canonical/pebble → 1.1.1 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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:

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)

Frequently Asked Questions

What is CVE-2024-3250? CVE-2024-3250 is a medium-severity missing authorization vulnerability in github.com/canonical/pebble (go), affecting versions >= 1.2.0, < 1.4.1. It is fixed in 1.4.2, 1.7.3, 1.10.2, 1.1.1. The application does not perform an authorization check before performing a sensitive operation.
How severe is CVE-2024-3250? CVE-2024-3250 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/canonical/pebble are affected by CVE-2024-3250? github.com/canonical/pebble (go) versions >= 1.2.0, < 1.4.1 is affected.
Is there a fix for CVE-2024-3250? Yes. CVE-2024-3250 is fixed in 1.4.2, 1.7.3, 1.10.2, 1.1.1. Upgrade to this version or later.
Is CVE-2024-3250 exploitable, and should I be worried? Whether CVE-2024-3250 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-3250 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-3250?
- Upgrade github.com/canonical/pebble to 1.4.2 or later
- Upgrade github.com/canonical/pebble to 1.7.3 or later
- Upgrade github.com/canonical/pebble to 1.10.2 or later
- Upgrade github.com/canonical/pebble to 1.1.1 or later