# CVE-2022-23292: Microsoft Power BI Spoofing Vulnerability

> An attacker can spoof information in Microsoft Power BI On-Premises Data Gateway, potentially misleading users or bypassing security controls.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Apr 2022
- **Updated:** 2 Jan 2025
- **Also known as:** GHSA-f6c2-x4hc-vxv2

## What is CVE-2022-23292?

CVE-2022-23292 is a low-severity vulnerability in Microsoft On-Premises Data Gateway, published on 15 Apr 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Microsoft Power BI Spoofing Vulnerability

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

It affects 1 product.


Products: Microsoft On-Premises Data Gateway.

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

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

## Is CVE-2022-23292 being exploited?

There is no known exploitation of CVE-2022-23292 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23292 is a low-severity vulnerability in Microsoft On-Premises Data Gateway, published on 15 Apr 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-23292 in the wild and no public exploit code.

Affected product: Microsoft On-Premises Data Gateway. 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-23292/ (Markdown: https://insights.sbomify.com/CVE-2022-23292/index.md)
```

## Sources

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

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