https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 13:38:19 +0000 https://cve.radiocsirt.org/vuln/cnvd-2020-27231 cnvd-2020-27231 https://cve.radiocsirt.org/vuln/cnvd-2020-27231 https://cve.radiocsirt.org/vuln/euvd-2026-40246 EUVD-2026-40246 https://cve.radiocsirt.org/vuln/euvd-2026-40246 https://cve.radiocsirt.org/vuln/fkie_cve-2020-11009 <p>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</p> <p>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</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-11009 https://cve.radiocsirt.org/vuln/ghsa-5679-7qrc-5m7j <p><strong>Affected:</strong> Maven: org.rundeck:rundeck</p> <p>### Impact</p> <p>Authenticated users can craft a request that reveals Execution data and logs and Job details that they are not authorized to see.</p> <p>&gt; 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.</p> <p>### Details</p> <p>An authenticated user could craft a request to:</p> <p>* 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…</p> <p><strong>Affected:</strong> Maven: org.rundeck:rundeck</p> <p>### Impact</p> <p>Authenticated users can craft a request that reveals Execution data and logs and Job details that they are not authorized to see.</p> <p>&gt; 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.</p> <p>### Details</p> <p>An authenticated user could craft a request to:</p> <p>* 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…</p> https://cve.radiocsirt.org/vuln/ghsa-5679-7qrc-5m7j https://cve.radiocsirt.org/vuln/gsd-2020-11009 gsd-2020-11009 https://cve.radiocsirt.org/vuln/gsd-2020-11009