CVE-2020-11009: Rundeck IDOR Can Reveal Execution Data Vulnerability

MODERATE
Advisory Identifier: GHSA-5679-7qrc-5m7j
CVSS 6.5
CWE-639 CWE-200
Published
Advisory Summary

CVE-2020-11009 is a MODERATE (CVSS 6.5) idor can reveal execution data vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting Rundeck libraries in the Maven ecosystem. The issue involves idor can reveal execution data and logs to unauthorized user in rundeck. Remediation is available by upgrading affected packages to version 3.2.6.

CVE-2020-11009 at a Glance

CVE Identifier CVE-2020-11009
GHSA Identifier GHSA-5679-7qrc-5m7j
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product Rundeck
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2020-11009

To remediate this vulnerability, upgrade all affected Rundeck dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.rundeck:rundeck fixed: 3.2.6
<dependency>
    <groupId>org.rundeck</groupId>
    <artifactId>rundeck</artifactId>
    <version>3.2.6</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.rundeck

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2020-11009, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.rundeck

Analyze the terminal output to locate any version of Rundeck in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.2.6), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.rundeck command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In Rundeck, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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. ### Details An authenticated user could craft a request to: * View Executions and download execution logs without access to `read` or `view` the associated Job, or ad-hoc resource. * Get the list of running executions in a project, without Event `read` access, if they have `read` access 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 `export` access level. * View the New User Profile Form for a different username, without User `admin` access. 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 `read` access to Events. * The Plugin Input Parameters for a SCM plugin would be sent without authorization for project `import`,`scm_import`,`export`, or `scm_export` actions. * Job Retry action could retry an execution without `read` or `view` access to the Execution, which would reveal the Execution's option values. (`run` access to the Job was still required). ### Patches Upgrade to Rundeck version 3.2.6 ### Workarounds None ### References [3.2.6 Release Notes](https://docs.rundeck.com/docs/history/3_2_x/version-3.2.6.html) ### Report If you have any questions or comments about this advisory: * Email us at [security@rundeck.com](mailto:security@rundeck.com) To report security issues to Rundeck please use the form at [http://rundeck.com/security](http://rundeck.com/security) Reporter: Justine Osborne of Apple Information Security

CVE-2020-11009 Affected Rundeck Versions

1 component(s)
Fixed Versions:
3.2.6
Product / Package Ecosystem Affected Versions Fixed Version
org.rundeck:rundeck
Maven
< 3.2.6
3.2.6

References

Frequently Asked Questions

What is CVE-2020-11009?
CVE-2020-11009 is a security vulnerability in Rundeck involving IDOR can reveal execution data and logs to unauthorized user in Rundeck under CWE-639: Authorization Bypass Through User-Controlled Key.
Which Rundeck versions are affected?
Affected versions include releases prior to 3.2.6 across affected packages: org.rundeck:rundeck.
What version fixes CVE-2020-11009?
Upgrading to 3.2.6 (or the latest patched release for your respective branch) resolves the vulnerability.
Is rundeck affected?
Yes, org.rundeck:rundeck is affected in releases prior to 3.2.6. Upgrade your dependency to 3.2.6 or later.
What is the CVSS score of CVE-2020-11009?
CVE-2020-11009 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2020-11009?
CVE-2020-11009 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check Maven dependencies for CVE-2020-11009?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.rundeck'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5679-7qrc-5m7j",
  "modified" : "2021-09-02T18:48:11Z",
  "published" : "2020-04-29T16:31:12Z",
  "aliases" : [ "CVE-2020-11009" ],
  "summary" : "IDOR can reveal execution data and logs to unauthorized user in Rundeck",
  "details" : "### Impact\n\nAuthenticated users can craft a request that reveals Execution data and logs  and Job details that they are not authorized to see.\n\n> 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.\n\n### Details\n\nAn authenticated user could craft a request to:\n\n* View Executions and download execution logs without access to `read` or `view` the associated Job, or ad-hoc resource.\n* Get the list of running executions in a project, without Event `read` access, if they have `read` access to view the project.\n* View the Options definitions of a Job without access to view the Job.\n* View the definition of a workflow step of a Job without access to view the Job.\n* View the SCM diff of a modified Job definition if SCM is enabled, without Project `export` access level.\n* View the New User Profile Form for a different username, without User `admin` access. 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.\n\nSome authenticated API requests were not correctly checking appropriate authorization levels:\n\n* The list of running Executions would be sent without `read` access to Events.\n* The Plugin Input Parameters for a SCM plugin would be sent without authorization for project `import`,`scm_import`,`export`, or `scm_export` actions.\n* Job Retry action could retry an execution without `read` or `view` access to the Execution, which would reveal the Execution's option values. (`run` access to the Job was still required).\n\n### Patches\nUpgrade to Rundeck version 3.2.6\n\n### Workarounds\nNone\n\n### References\n[3.2.6 Release Notes](https://docs.rundeck.com/docs/history/3_2_x/version-3.2.6.html)\n\n### Report\nIf you have any questions or comments about this advisory:\n* Email us at [security@rundeck.com](mailto:security@rundeck.com)\n\nTo report security issues to Rundeck please use the form at [http://rundeck.com/security](http://rundeck.com/security)\n\nReporter: Justine Osborne of Apple Information Security",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.rundeck:rundeck"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.2.6"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/rundeck/rundeck/security/advisories/GHSA-5679-7qrc-5m7j"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2020-11009"
  }, {
    "type" : "WEB",
    "url" : "https://docs.rundeck.com/docs/history/3_2_x/version-3.2.6.html"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/rundeck/rundeck"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-639" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-04-29T16:30:45Z",
    "nvd_published_at" : "2020-04-29T17:15:00Z"
  }
}