{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36118 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-36118 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-36118 is a medium-severity missing authorization vulnerability in n/a, published on 25 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-36118 and fix it if it is affected.\n\nWhat it is: CVE-2022-36118 is a medium-severity missing authorization vulnerability in n/a, published on 25 Aug 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-2022-36118 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-36118/ (Markdown: https://insights.sbomify.com/CVE-2022-36118/index.md)","id":"CVE-2022-36118","markdown":"https://insights.sbomify.com/CVE-2022-36118/index.md","name":"CVE-2022-36118","record":{"aliases":["GHSA-c7j5-c9cg-4fgg"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Blue Prism Enterprise","requires_auth":"low_privilege","summary":"Authenticated users can bypass access controls to modify process statuses in Blue Prism Enterprise if the application server is misconfigured.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"blue_prism","vendor":"ssctech"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N","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 the SetProcessAttributes administrative function. Abusing this function will allow any Blue Prism user to publish, unpublish, or retire processes. Using this function, any logged-in user can change the status of a process, an action allowed only intended for users with the Edit Process permission.","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":"Missing authorization in n/a","id":"CVE-2022-36118","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Deserialization in n/a","id":"CVE-2022-36119"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2022-36117"},"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":7.1,"headline":"Code injection in n/a","id":"CVE-2022-36115","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":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 bypass access controls to modify process statuses in Blue Prism Enterprise if the application server is misconfigured.","url":"https://insights.sbomify.com/CVE-2022-36118/"}