# CVE-2022-47636: Other in n/a

> Attackers can execute arbitrary code by placing malicious DLLs in the directory of a .oml file opened by the user.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Aug 2023
- **Updated:** 10 Oct 2024
- **Also known as:** GHSA-fpxq-878r-vmwf

## What is CVE-2022-47636?

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.

### Official 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.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2022-47636?

It affects 1 product.


Products: Outsystems Service Studio.

## How do I fix CVE-2022-47636?

No fix has been published for CVE-2022-47636 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-47636 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47636 exists.

Public exploit code:

- OutSystems Service Studio 11.53.30 - DLL Hijacking (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-47636 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47636 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-47636/ (Markdown: https://insights.sbomify.com/CVE-2022-47636/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-47636
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-47636
- OSV: https://osv.dev/vulnerability/CVE-2022-47636

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-47636/
Summaries are generated and may contain mistakes; the official description above is the record.