{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-44009 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-44009 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-44009 is a high-severity missing authorization vulnerability in n/a, published on 5 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-44009 and fix it if it is affected.\n\nWhat it is: CVE-2022-44009 is a high-severity missing authorization vulnerability in n/a, published on 5 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-44009 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2022-44009/ (Markdown: https://insights.sbomify.com/CVE-2022-44009/index.md)","id":"CVE-2022-44009","markdown":"https://insights.sbomify.com/CVE-2022-44009/index.md","name":"CVE-2022-44009","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"StackStorm automation platform","requires_auth":"none","summary":"Attackers can bypass RBAC checks in Jinja filters to access other users' sensitive key-value pairs in StackStorm.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"stackstorm","vendor":"stackstorm"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Improper access control in Key-Value RBAC in StackStorm version 3.7.0 didn't check the permissions in Jinja filters, allowing attackers to access K/V pairs of other users, potentially leading to the exposure of sensitive Information.","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":"Missing authorization in n/a","id":"CVE-2022-44009","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2022-44010"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2022-44008"},"products":["n/a"],"published":"2022-12-05","related":[{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2021-44657","kev_date_added":null,"published":"2021-12-15"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2021-28667","kev_date_added":null,"published":"2021-03-18"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-9580","kev_date_added":null,"published":"2019-03-09"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2022-43706","kev_date_added":null,"published":"2022-12-05"},{"cvss_score":5.3,"headline":"Missing authorization in n/a","id":"CVE-2018-20345","kev_date_added":null,"published":"2018-12-21"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-24","vendors":["n/a"]},"summary":"Attackers can bypass RBAC checks in Jinja filters to access other users' sensitive key-value pairs in StackStorm.","url":"https://insights.sbomify.com/CVE-2022-44009/"}