| Gói / sản phẩm | Phiên bản bị ảnh hưởng | Phiên bản đã vá |
|---|---|---|
| github.com/fleetdm/fleet | ≥ 4.75.0, < 4.75.2≥ 4.76.0, < 4.76.2≥ 4.77.0, < 4.77.1≥ 4.78.0, < 4.78.3 | 4.75.24.76.24.77.14.78.3 |
| github.com/fleetdm/fleet/v4 | ≥ 4.75.0, < 4.75.2≥ 4.76.0, < 4.76.2≥ 4.77.0, < 4.77.1≥ 4.78.0, < 4.78.3< 4.78.3-0.20260112221730-5c030e32a3a9 | 4.75.24.76.24.77.14.78.34.78.3-0.20260112221730-5c030e32a3a9 |
| fleet | = 4.77.0≥ 4.75.0, < 4.75.2≥ 4.76.0, < 4.76.2≥ 4.78.0, < 4.78.3< 4.53.3 | 4.75.24.76.24.78.34.53.3 |
A broken access control issue in Fleet 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.
If an immediate upgrade is not possible, users should put the debug/pprof endpoints behind an IP allowlist.
If you have any questions or comments about this advisory:
Email us at [email protected] Join #fleet in osquery Slack
We thank @secfox-ai for responsibly reporting this issue.
Bạn đang dùng một trong các sản phẩm này? Quét site để biết có đang lộ phiên bản có lỗ hổng không.
Quét site miễn phí