{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47636 exists.","fix":"No fix has been published for CVE-2022-47636 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-47636 is a high-severity vulnerability in n/a, published on 10 Aug 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-47636 and fix it if it is affected.\n\nWhat it is: CVE-2022-47636 is a high-severity vulnerability in n/a, published on 10 Aug 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-2022-47636 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-47636/ (Markdown: https://insights.sbomify.com/CVE-2022-47636/index.md)","id":"CVE-2022-47636","markdown":"https://insights.sbomify.com/CVE-2022-47636/index.md","name":"CVE-2022-47636","record":{"aliases":["GHSA-fpxq-878r-vmwf"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"OutSystems Service Studio","requires_auth":"none","summary":"Attackers can execute arbitrary code by placing malicious DLLs in the directory of a .oml file opened by the user.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"service_studio","vendor":"outsystems"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"A DLL hijacking vulnerability has been discovered in OutSystems Service Studio 11 11.53.30 build 61739. When a user open a .oml file (OutSystems Modeling Language), the application will load the following DLLs from the same directory av_libGLESv2.dll, libcef.DLL, user32.dll, and d3d10warp.dll. Using a crafted DLL, it is possible to execute arbitrary code in the context of the current logged in user.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2023-08-10","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-08-10","kind":"exploitdb","ref":"51678","stars":null,"title":"OutSystems Service Studio 11.53.30 - DLL Hijacking"}],"tier":"weaponised"},"has_fix":null,"headline":"Other in n/a","id":"CVE-2022-47636","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2022-47637"},"packages":[],"prev":{"headline":"Server-side request forgery in n/a","id":"CVE-2022-47635"},"products":["n/a"],"published":"2023-08-10","related":[],"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":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-10","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code by placing malicious DLLs in the directory of a .oml file opened by the user.","url":"https://insights.sbomify.com/CVE-2022-47636/"}