{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41111 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-41111 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-41111 is a medium-severity missing authorization vulnerability in rundeck, published on 28 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-41111 and fix it if it is affected.\n\nWhat it is: CVE-2021-41111 is a medium-severity missing authorization vulnerability in rundeck, published on 28 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-41111 in the wild and no public exploit code.\n\nAffected product: rundeck. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-41111/ (Markdown: https://insights.sbomify.com/CVE-2021-41111/index.md)","id":"CVE-2021-41111","markdown":"https://insights.sbomify.com/CVE-2021-41111/index.md","name":"CVE-2021-41111","record":{"aliases":["GHSA-mfqj-f22m-gv8j"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Rundeck automation service","requires_auth":"low_privilege","summary":"Authenticated users can bypass project isolation to read webhook definitions and tokens from other projects, potentially triggering sensitive actions.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"rundeck","vendor":"pagerduty"}],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Rundeck is an open source automation service with a web console, command line tools and a WebAPI. Prior to versions 3.4.5 and 3.3.15, an authenticated user with authorization to read webhooks in one project can craft a request to reveal Webhook definitions and tokens in another project. The user could use the revealed webhook tokens to trigger webhooks. Severity depends on trust level of authenticated users and whether any webhooks exist that trigger sensitive actions. There are patches for this vulnerability in versions 3.4.5 and 3.3.15. There are currently no known workarounds.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Authorization Bypass Through User-Controlled Key in Rundeck","id":"CVE-2021-41111","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Missing Authorization in Rundeck","id":"CVE-2021-41112"},"packages":[],"prev":{"headline":"CWL Viewer: deserialization of untrusted data can lead to complete takeover by an attacker","id":"CVE-2021-41110"},"products":["rundeck"],"published":"2022-02-28","related":[{"cvss_score":9.1,"headline":"Use of Hard-coded Cryptographic Key in rundeck/rundeck, rundeckpro/enterprise","id":"CVE-2022-29186","kev_date_added":null,"published":"2022-05-20"},{"cvss_score":8.8,"headline":"YAML deserialization can run untrusted code","id":"CVE-2021-39132","kev_date_added":null,"published":"2021-08-30"},{"cvss_score":8.1,"headline":"Authenticated users can view or delete jobs they do not have authorization for in Rundeck","id":"CVE-2023-48222","kev_date_added":null,"published":"2023-11-16"},{"cvss_score":8.1,"headline":"Missing Authorization in Rundeck","id":"CVE-2021-41112","kev_date_added":null,"published":"2022-02-28"},{"cvss_score":7.5,"headline":"Plaintext Storage of Keys and Passwords in Rundeck and PagerDuty Process Automation","id":"CVE-2022-31044","kev_date_added":null,"published":"2022-06-15"},{"cvss_score":7.2,"headline":"Cross-Site Request Forgery (CSRF) can run untrusted code on Rundeck server","id":"CVE-2021-39133","kev_date_added":null,"published":"2021-08-30"},{"cvss_score":6.5,"headline":"IDOR can reveal execution data and logs to unauthorized user in Rundeck","id":"CVE-2020-11009","kev_date_added":null,"published":"2020-04-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["rundeck"]},"summary":"Authenticated users can bypass project isolation to read webhook definitions and tokens from other projects, potentially triggering sensitive actions.","url":"https://insights.sbomify.com/CVE-2021-41111/"}