No authorisation controls in the RestAPI documentation for Tribe29s Checkmk <= 2.1.0p13 and Checkmk <= 2.0.0p29 which may lead to unintended information disclosure through automatically generated user specific tags within Rest API documentation.
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Checkmk | Checkmk | 2.1.0 (including) | 2.1.0 (including) |
Checkmk | Checkmk | 2.1.0-b1 (including) | 2.1.0-b1 (including) |
Checkmk | Checkmk | 2.1.0-b2 (including) | 2.1.0-b2 (including) |
Checkmk | Checkmk | 2.1.0-b3 (including) | 2.1.0-b3 (including) |
Checkmk | Checkmk | 2.1.0-b4 (including) | 2.1.0-b4 (including) |
Checkmk | Checkmk | 2.1.0-b5 (including) | 2.1.0-b5 (including) |
Checkmk | Checkmk | 2.1.0-b6 (including) | 2.1.0-b6 (including) |
Checkmk | Checkmk | 2.1.0-b7 (including) | 2.1.0-b7 (including) |
Checkmk | Checkmk | 2.1.0-b8 (including) | 2.1.0-b8 (including) |
Checkmk | Checkmk | 2.1.0-b9 (including) | 2.1.0-b9 (including) |
Checkmk | Checkmk | 2.1.0-p1 (including) | 2.1.0-p1 (including) |
Checkmk | Checkmk | 2.1.0-p10 (including) | 2.1.0-p10 (including) |
Checkmk | Checkmk | 2.1.0-p11 (including) | 2.1.0-p11 (including) |
Checkmk | Checkmk | 2.1.0-p12 (including) | 2.1.0-p12 (including) |
Checkmk | Checkmk | 2.1.0-p13 (including) | 2.1.0-p13 (including) |
Checkmk | Checkmk | 2.1.0-p2 (including) | 2.1.0-p2 (including) |
Checkmk | Checkmk | 2.1.0-p3 (including) | 2.1.0-p3 (including) |
Checkmk | Checkmk | 2.1.0-p4 (including) | 2.1.0-p4 (including) |
Checkmk | Checkmk | 2.1.0-p5 (including) | 2.1.0-p5 (including) |
Checkmk | Checkmk | 2.1.0-p6 (including) | 2.1.0-p6 (including) |
Checkmk | Checkmk | 2.1.0-p7 (including) | 2.1.0-p7 (including) |
Checkmk | Checkmk | 2.1.0-p8 (including) | 2.1.0-p8 (including) |
Checkmk | Checkmk | 2.1.0-p9 (including) | 2.1.0-p9 (including) |
Check-mk | Ubuntu | bionic | * |
Check-mk | Ubuntu | trusty | * |
Check-mk | Ubuntu | xenial | * |
Assuming a user with a given identity, authorization is the process of determining whether that user can access a given resource, based on the user’s privileges and any permissions or other access-control specifications that apply to the resource. When access control checks are not applied, users are able to access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures, denial of service, and arbitrary code execution.