Summary
IDOR can reveal execution data and logs to unauthorized user in Rundeck
Details
An authenticated user could craft a request to:
- View Executions and download execution logs without access to
readorviewthe associated Job, or ad-hoc resource. - Get the list of running executions in a project, without Event
readaccess, if they havereadaccess to view the project. - View the Options definitions of a Job without access to view the Job.
- View the definition of a workflow step of a Job without access to view the Job.
- View the SCM diff of a modified Job definition if SCM is enabled, without Project
exportaccess level. - View the New User Profile Form for a different username, without User
adminaccess. Note: they would not be allowed to create or modify a profile for a different user, or reveal any user profile information for a different user.
Some authenticated API requests were not correctly checking appropriate authorization levels:
- The list of running Executions would be sent without
readaccess to Events. - The Plugin Input Parameters for a SCM plugin would be sent without authorization for project
import,scm_import,export, orscm_exportactions. - Job Retry action could retry an execution without
readorviewaccess to the Execution, which would reveal the Execution's option values. (runaccess to the Job was still required).
Workarounds
None
References
Report
If you have any questions or comments about this advisory:
- Email us at [email protected]
To report security issues to Rundeck please use the form at http://rundeck.com/security
Reporter: Justine Osborne of Apple Information Security
Impact
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.
CVE-2020-11009 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.2.6); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Upgrade to Rundeck version 3.2.6
Frequently Asked Questions
- What is CVE-2020-11009? CVE-2020-11009 is a medium-severity security vulnerability in org.rundeck:rundeck (maven), affecting versions < 3.2.6. It is fixed in 3.2.6.
- How severe is CVE-2020-11009? CVE-2020-11009 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.rundeck:rundeck are affected by CVE-2020-11009? org.rundeck:rundeck (maven) versions < 3.2.6 is affected.
- Is there a fix for CVE-2020-11009? Yes. CVE-2020-11009 is fixed in 3.2.6. Upgrade to this version or later.
- Is CVE-2020-11009 exploitable, and should I be worried? Whether CVE-2020-11009 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2020-11009 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2020-11009? Upgrade
org.rundeck:rundeckto 3.2.6 or later.