{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36115 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-36115 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-36115 is a high-severity code injection vulnerability in n/a, published on 25 Aug 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-36115 and fix it if it is affected.\n\nWhat it is: CVE-2022-36115 is a high-severity code injection vulnerability in n/a, published on 25 Aug 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-36115 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-36115/ (Markdown: https://insights.sbomify.com/CVE-2022-36115/index.md)","id":"CVE-2022-36115","markdown":"https://insights.sbomify.com/CVE-2022-36115/index.md","name":"CVE-2022-36115","record":{"aliases":["GHSA-frqm-x2fh-hcwr"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Blue Prism Enterprise","requires_auth":"low_privilege","summary":"Authenticated users can inject malicious code into Blue Prism workflows via CreateProcessAutosave, potentially executing it in production if not reviewed.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"blue_prism","vendor":"ssctech"}],"cvss":{"score":7.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"An issue was discovered in Blue Prism Enterprise 6.0 through 7.01. In a misconfigured environment that exposes the Blue Prism Application server, it is possible for an authenticated user to reverse engineer the Blue Prism software and circumvent access controls for unintended functionality. An attacker can abuse the CreateProcessAutosave() method to inject their own functionality into a development process. If (upon a warning) a user decides to recover unsaved work by using the last saved version, the malicious code could enter the workflow. Should the process action stages not be fully reviewed before publishing, this could result in the malicious code being run in a production environment.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2022-36115","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2022-36116"},"packages":[],"prev":{"headline":"Extracting malicious crates can fill the file system","id":"CVE-2022-36114"},"products":["n/a"],"published":"2022-08-25","related":[{"cvss_score":8.8,"headline":"Deserialization in n/a","id":"CVE-2022-36119","kev_date_added":null,"published":"2022-08-25"},{"cvss_score":5.3,"headline":"Security feature bypass in n/a","id":"CVE-2022-36116","kev_date_added":null,"published":"2022-08-25"},{"cvss_score":5.3,"headline":"Missing authorization in n/a","id":"CVE-2022-36118","kev_date_added":null,"published":"2022-08-25"},{"cvss_score":3.1,"headline":"Security feature bypass in n/a","id":"CVE-2022-36117","kev_date_added":null,"published":"2022-08-25"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Authenticated users can inject malicious code into Blue Prism workflows via CreateProcessAutosave, potentially executing it in production if not reviewed.","url":"https://insights.sbomify.com/CVE-2022-36115/"}