First published: Wed Apr 29 2020(Updated: )
In Rundeck before version 3.2.6, authenticated users can craft a request that reveals Execution data and logs and Job details that they are not authorized to see. Depending on the configuration and the way that Rundeck is used, this could result in anything between a high severity risk, or a very low risk. If access is tightly restricted and all users on the system have access to all projects, this is not really much of an issue. If access is wider and allows login for users that do not have access to any projects, or project access is restricted, there is a larger issue. If access is meant to be restricted and secrets, sensitive data, or intellectual property are exposed in Rundeck execution output and job data, the risk becomes much higher. This vulnerability is patched in version 3.2.6
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Pagerduty Rundeck | <3.2.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this vulnerability is CVE-2020-11009.
The severity of CVE-2020-11009 is medium with a severity value of 6.5.
Authenticated users can craft a request that reveals execution data and logs and job details that they are not authorized to see.
The affected software is Pagerduty Rundeck version up to, but excluding, 3.2.6.
To fix CVE-2020-11009, update to Rundeck version 3.2.6 or later.