Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-5679-7qrc-5m7j

MEDIUM

GHSA-5679-7qrc-5m7j is a medium-severity (CVSS 6.5) Information Exposure vulnerability in org.rundeck:rundeck. O3 Security confirms whether GHSA-5679-7qrc-5m7j is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

IDOR can reveal execution data and logs to unauthorized user in Rundeck

Also known asCVE-2020-11009
Published
Apr 29, 2020
Updated
Mar 13, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected
org.rundeck:rundeck

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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

Report

If you have any questions or comments about this advisory:

To report security issues to Rundeck please use the form at http://rundeck.com/security

Reporter: Justine Osborne of Apple Information Security

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.rundeck:rundeckall versions3.2.6

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.rundeck:rundeck. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.rundeck:rundeck to 3.2.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5679-7qrc-5m7j is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-5679-7qrc-5m7j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-5679-7qrc-5m7j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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 an
O3 Security · Impact-Aware SCA

Is GHSA-5679-7qrc-5m7j in your dependencies?

O3 detects GHSA-5679-7qrc-5m7j across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.