# CVE-2020-11009: IDOR can reveal execution data and logs to unauthorized user in Rundeck > Authenticated users can access unauthorized execution data and logs via IDOR, exposing sensitive information in Rundeck. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 29 Apr 2020 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-5679-7qrc-5m7j ## What is CVE-2020-11009? CVE-2020-11009 is a medium-severity missing authorization vulnerability in rundeck, published on 29 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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 Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2020-11009? 2 open source packages ship an affected version, including org.rundeck:rundeck. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.rundeck:rundeck` | Maven | All versions | 3.2.6 | | `org.rundeck:rundeck` | Maven | All versions | 3.2.6 | Products: Pagerduty Rundeck. ## How do I fix CVE-2020-11009? Upgrade org.rundeck:rundeck to 3.2.6 or later. ## Is CVE-2020-11009 being exploited? There is no known exploitation of CVE-2020-11009 in the wild and no public exploit code. ## Other vulnerabilities in rundeck - [CVE-2022-29186](https://insights.sbomify.com/CVE-2022-29186/): Use of Hard-coded Cryptographic Key in rundeck/rundeck, rundeckpro/enterprise (critical 9.1) - [CVE-2021-39132](https://insights.sbomify.com/CVE-2021-39132/): YAML deserialization can run untrusted code (high 8.8) - [CVE-2023-48222](https://insights.sbomify.com/CVE-2023-48222/): Authenticated users can view or delete jobs they do not have authorization for in Rundeck (high 8.1) - [CVE-2021-41112](https://insights.sbomify.com/CVE-2021-41112/): Missing Authorization in Rundeck (high 8.1) - [CVE-2022-31044](https://insights.sbomify.com/CVE-2022-31044/): Plaintext Storage of Keys and Passwords in Rundeck and PagerDuty Process Automation (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-11009 and fix it if it is affected. What it is: CVE-2020-11009 is a medium-severity missing authorization vulnerability in rundeck, published on 29 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-11009 in the wild and no public exploit code. Affected packages and fixed versions: - org.rundeck:rundeck (Maven): affected all versions; fixed in 3.2.6 - org.rundeck:rundeck (Maven): affected all versions; fixed in 3.2.6 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-11009/ (Markdown: https://insights.sbomify.com/CVE-2020-11009/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-11009 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-11009 - OSV: https://osv.dev/vulnerability/CVE-2020-11009 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-11009/ Summaries are generated and may contain mistakes; the official description above is the record.