Fleet has an Access Control vulnerability in debug/pprof endpoints
fleetdm fleet
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/fleetdm/fleet Go |
|
|
fleetdm fleet
| Product | Affected | Fixed in |
|---|---|---|
| github.com/fleetdm/fleet Go |
|
|
| github.com/fleetdm/fleet/v4 Go |
|
|
Fleet is open source device management software. A broken access control issue in versions prior to 4.78.3, 4.77.1, 4.76.2, 4.75.2, and 4.53.3 allowed authenticated users to access debug and profiling endpoints regardless of role. As a result, low-privilege users could view internal server diagnostics and trigger resource-intensive profiling operations. Fleet’s debug/pprof endpoints are accessible to any authenticated user regardless of role, including the lowest-privilege “Observer” role. This allows low-privilege users to access sensitive server internals, including runtime profiling data and in-memory application state, and to trigger CPU-intensive profiling operations that could lead to denial of service. Versions 4.78.3, 4.77.1, 4.76.2, 4.75.2, and 4.53.3 fix the issue. If an immediate upgrade is not possible, users should put the debug/pprof endpoints behind an IP allowlist as a workaround.
From the CVE record · GitHub_M
Fleet’s debug/pprof endpoints allow any authenticated user, including an Observer, to access them regardless of role. A low-privilege user can view internal server diagnostics and in-memory application state, and trigger CPU-intensive profiling that could lead to denial of service.
Teams running Fleet versions prior to the applicable fixes—4.78.3, 4.77.1, 4.76.2, 4.75.2, or 4.53.3—or using the affected Go packages should check their installations.