{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-48225 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-48225 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-48225 is a high-severity vulnerability in n/a, published on 4 Apr 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-2022-48225 and fix it if it is affected.\n\nWhat it is: CVE-2022-48225 is a high-severity vulnerability in n/a, published on 4 Apr 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: There is no known exploitation of CVE-2022-48225 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-48225/ (Markdown: https://insights.sbomify.com/CVE-2022-48225/index.md)","id":"CVE-2022-48225","markdown":"https://insights.sbomify.com/CVE-2022-48225/index.md","name":"CVE-2022-48225","record":{"aliases":["GHSA-9p85-c2hf-rxr2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Acuant AcuFill SDK","requires_auth":"low_privilege","summary":"Attackers can achieve privilege escalation and code execution via DLL hijacking in the Gemalto Document Reader installation process.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"acuant_acufill_sdk","vendor":"gbgplc"}],"cvss":{"score":7.3,"severity":"high","source":"nvd","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":"An issue was discovered in Acuant AcuFill SDK before 10.22.02.03. It is used to install drivers from several different vendors. The Gemalto Document Reader child installation process is vulnerable to DLL hijacking, because it attempts to execute (with elevated privileges) multiple non-existent DLLs out of a non-existent standard-user writable location.","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-48225","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2022-48226"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2022-48224"},"products":["n/a"],"published":"2023-04-04","related":[{"cvss_score":8.4,"headline":"Privilege escalation in n/a","id":"CVE-2022-48226","kev_date_added":null,"published":"2023-04-04"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2022-48222","kev_date_added":null,"published":"2023-04-04"},{"cvss_score":7.5,"headline":"Race condition in n/a","id":"CVE-2022-48221","kev_date_added":null,"published":"2023-04-04"},{"cvss_score":7.3,"headline":"Privilege escalation in n/a","id":"CVE-2022-48224","kev_date_added":null,"published":"2023-04-04"},{"cvss_score":6.7,"headline":"Other in n/a","id":"CVE-2022-48223","kev_date_added":null,"published":"2023-04-04"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-18","vendors":["n/a"]},"summary":"Attackers can achieve privilege escalation and code execution via DLL hijacking in the Gemalto Document Reader installation process.","url":"https://insights.sbomify.com/CVE-2022-48225/"}