# CVE-2021-38175: Information disclosure in SAP Analysis for Microsoft Office

> High-privilege attackers can read sensitive data and modify system information in SAP Analysis for Microsoft Office without user interaction.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5hf5-x5wx-5v9c

## What is CVE-2021-38175?

CVE-2021-38175 is a medium-severity vulnerability in SAP Analysis for Microsoft Office, published on 14 Sep 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SAP Analysis for Microsoft Office - version 2.8, allows an attacker with high privileges to read sensitive data over the network, and gather or change information in the current system without user interaction. The attack would not lead to an impact on the availability of the system, but there would be an impact on integrity and confidentiality.

## Which versions are affected by CVE-2021-38175?

It affects 1 product.


Products: Sap Analysis for Microsoft Office.

## How do I fix CVE-2021-38175?

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

## Is CVE-2021-38175 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-38175 and fix it if it is affected.

What it is: CVE-2021-38175 is a medium-severity vulnerability in SAP Analysis for Microsoft Office, published on 14 Sep 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-38175 in the wild and no public exploit code.

Affected product: SAP Analysis for Microsoft Office. 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-2021-38175/ (Markdown: https://insights.sbomify.com/CVE-2021-38175/index.md)
```

## Sources

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

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