GHSA-5679-7qrc-5m7j — rundeck
MEDIUMGHSA-5679-7qrc-5m7j is a medium-severity (CVSS 6.5) Information Exposure vulnerability in org.rundeck:rundeck. A fix is available for org.rundeck:rundeck — see the affected versions and patch details below.
IDOR can reveal execution data and logs to unauthorized user in Rundeck
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-5679-7qrc-5m7j plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,238 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.rundeck:rundeckReal-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
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).
Patches
Upgrade to Rundeck version 3.2.6
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.rundeck:rundeck | all versions | 3.2.6org.rundeck:rundeck:3.2.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.rundeck:rundeck, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5679-7qrc-5m7j can be triaged on real exposure rather than presence alone.
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
Is GHSA-5679-7qrc-5m7j in your dependencies?
O3 Security finds GHSA-5679-7qrc-5m7j across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.