The Periodic Backup Plugin did not perform any permission checks, allowing any user with Overall/Read access to change its settings, trigger backups, restore backups, download backups, and also delete all previous backups via log rotation. Additionally, the plugin was not requiring requests to its API be sent via POST, thereby opening itself to Cross-Site Request Forgery attacks.
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 |
---|---|---|---|
Periodic_backup | Jenkins | 1.0 (including) | 1.0 (including) |
Periodic_backup | Jenkins | 1.1 (including) | 1.1 (including) |
Periodic_backup | Jenkins | 1.2 (including) | 1.2 (including) |
Periodic_backup | Jenkins | 1.3 (including) | 1.3 (including) |
Periodic_backup | Jenkins | 1.4 (including) | 1.4 (including) |
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.