{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-45183 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-45183 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-45183 is a high-severity vulnerability in n/a, published on 14 Nov 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-45183 and fix it if it is affected.\n\nWhat it is: CVE-2022-45183 is a high-severity vulnerability in n/a, published on 14 Nov 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-45183 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-45183/ (Markdown: https://insights.sbomify.com/CVE-2022-45183/index.md)","id":"CVE-2022-45183","markdown":"https://insights.sbomify.com/CVE-2022-45183/index.md","name":"CVE-2022-45183","record":{"aliases":["GHSA-6rgm-phq5-f5ww"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PowerShell Universal","requires_auth":"low_privilege","summary":"An attacker with a valid app token can retrieve other app tokens via HTTP requests, leading to privilege escalation in PowerShell Universal.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"powershell_universal","vendor":"ironmansoftware"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"Escalation of privileges in the Web Server in Ironman Software PowerShell Universal 2.x and 3.x allows an attacker with a valid app token to retrieve other app tokens by ID via an HTTP web request. Patched Versions are 3.5.3, 3.4.7, and 2.12.6.","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":"Privilege escalation in n/a","id":"CVE-2022-45183","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Path traversal in n/a","id":"CVE-2022-45184"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2022-45182"},"products":["n/a"],"published":"2022-11-14","related":[{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2023-49213","kev_date_added":null,"published":"2023-11-23"},{"cvss_score":8.3,"headline":"Missing authorization in PowerShell Universal","id":"CVE-2026-4064","kev_date_added":null,"published":"2026-03-17"},{"cvss_score":7.2,"headline":"Path traversal in n/a","id":"CVE-2022-45184","kev_date_added":null,"published":"2022-11-14"},{"cvss_score":6.1,"headline":"Cross-site scripting in PowerShell Universal","id":"CVE-2026-0618","kev_date_added":null,"published":"2026-01-07"},{"cvss_score":5.5,"headline":"Denial of service in PowerShell Universal","id":"CVE-2026-3563","kev_date_added":null,"published":"2026-03-17"},{"cvss_score":5.5,"headline":"Hardcoded credentials in PowerShell Universal","id":"CVE-2026-3277","kev_date_added":null,"published":"2026-02-27"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"An attacker with a valid app token can retrieve other app tokens via HTTP requests, leading to privilege escalation in PowerShell Universal.","url":"https://insights.sbomify.com/CVE-2022-45183/"}