{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-44875 exists.","fix":"No fix has been published for CVE-2022-44875 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-44875 is a medium-severity code injection vulnerability in n/a, published on 6 Mar 2023. 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-44875 and fix it if it is affected.\n\nWhat it is: CVE-2022-44875 is a medium-severity code injection vulnerability in n/a, published on 6 Mar 2023. Any signed-in user can exploit it over the 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-2022-44875 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-2022-44875/ (Markdown: https://insights.sbomify.com/CVE-2022-44875/index.md)","id":"CVE-2022-44875","markdown":"https://insights.sbomify.com/CVE-2022-44875/index.md","name":"CVE-2022-44875","record":{"aliases":["GHSA-fw7h-2grr-4rjq"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Kiosk browser software","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code with SYSTEM privileges via JavaScript injection in KioWare kiosk browser due to permissive ACL settings.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"kioware","vendor":"kioware"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"KioWare through 8.33 on Windows sets KioScriptingUrlACL.AclActions.AllowHigh for the about:blank origin, which allows attackers to obtain SYSTEM access via KioUtils.Execute in JavaScript code.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2023-07-20","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-07-20T14:30:58Z","kind":"github_poc","ref":"https://github.com/AesirSec/CVE-2022-44875-Test","stars":0,"title":"Testing CVE-2022-44875"}],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2022-44875","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"CWP Control Web Panel OS Command Injection","id":"CVE-2022-44877"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2022-44874"},"products":["n/a"],"published":"2023-03-06","related":[{"cvss_score":8.4,"headline":"Security feature bypass in Kioware","id":"CVE-2024-3459","kev_date_added":null,"published":"2024-05-09"},{"cvss_score":7.8,"headline":"Security feature bypass in n/a","id":"CVE-2023-34641","kev_date_added":null,"published":"2023-06-19"},{"cvss_score":7.8,"headline":"Command injection in n/a","id":"CVE-2023-34642","kev_date_added":null,"published":"2023-06-19"},{"cvss_score":7.4,"headline":"Security feature bypass in Kioware","id":"CVE-2024-3460","kev_date_added":null,"published":"2024-05-09"},{"cvss_score":6.2,"headline":"Security feature bypass in Kioware","id":"CVE-2024-3461","kev_date_added":null,"published":"2024-05-09"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-06","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code with SYSTEM privileges via JavaScript injection in KioWare kiosk browser due to permissive ACL settings.","url":"https://insights.sbomify.com/CVE-2022-44875/"}