{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22947 exists.","fix":"No fix has been published for CVE-2023-22947 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-22947 is a high-severity vulnerability in n/a, published on 11 Jan 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-22947 and fix it if it is affected.\n\nWhat it is: CVE-2023-22947 is a high-severity vulnerability in n/a, published on 11 Jan 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22947 exists.\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-2023-22947/ (Markdown: https://insights.sbomify.com/CVE-2023-22947/index.md)","id":"CVE-2023-22947","markdown":"https://insights.sbomify.com/CVE-2023-22947/index.md","name":"CVE-2023-22947","record":{"aliases":["GHSA-fc86-55vx-x268"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Shibboleth Service Provider","requires_auth":"low_privilege","summary":"An unprivileged local attacker can escalate privileges to SYSTEM via DLL planting due to insecure default folder permissions in the Windows installation path.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"service_provider","vendor":"shibboleth"}],"cvss":{"score":7.3,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"Insecure folder permissions in the Windows installation path of Shibboleth Service Provider (SP) before 3.4.1 allow an unprivileged local attacker to escalate privileges to SYSTEM via DLL planting in the service executable's folder. This occurs because the installation goes under C:\\opt (rather than C:\\Program Files) by default. NOTE: the vendor disputes the significance of this report, stating that \"We consider the ACLs a best effort thing\" and \"it was a documentation mistake.\"","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2023-22947","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2023-22948"},"packages":[],"prev":{"headline":"Apache Spark proxy-user privilege escalation from malicious configuration class","id":"CVE-2023-22946"},"products":["n/a"],"published":"2023-01-11","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2019-19191","kev_date_added":null,"published":"2019-11-21"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2021-31826","kev_date_added":null,"published":"2021-04-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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-07","vendors":["n/a"]},"summary":"An unprivileged local attacker can escalate privileges to SYSTEM via DLL planting due to insecure default folder permissions in the Windows installation path.","url":"https://insights.sbomify.com/CVE-2023-22947/"}