# CVE-2017-0197: Code injection in Office

> Remote attackers can execute arbitrary code by tricking users into opening a crafted OneNote document, requiring immediate patching.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 12 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gcvm-v83h-fhq2

## What is CVE-2017-0197?

CVE-2017-0197 is a high-severity code injection vulnerability in Microsoft Corporation Office, published on 12 Apr 2017. 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

Microsoft OneNote 2007 SP3 and Microsoft OneNote 2010 SP2 allow remote attackers to execute arbitrary code via a crafted document, aka "Microsoft Office DLL Loading Vulnerability."

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-0197?

It affects 1 product.


Products: Microsoft Onenote.

## How do I fix CVE-2017-0197?

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

## Is CVE-2017-0197 being exploited?

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

## Other vulnerabilities in Microsoft Corporation Office

- [CVE-2014-2815](https://insights.sbomify.com/CVE-2014-2815/): Code injection in n/a (high 8.8)
- [CVE-2024-41159](https://insights.sbomify.com/CVE-2024-41159/): Privilege escalation in OneNote (high 7.1)
- [CVE-2023-33140](https://insights.sbomify.com/CVE-2023-33140/): Microsoft OneNote Spoofing Vulnerability (medium 6.5)
- [CVE-2023-21721](https://insights.sbomify.com/CVE-2023-21721/): Microsoft OneNote Elevation of Privilege Vulnerability (medium 6.5)
- [CVE-2016-3315](https://insights.sbomify.com/CVE-2016-3315/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-0197 and fix it if it is affected.

What it is: CVE-2017-0197 is a high-severity code injection vulnerability in Microsoft Corporation Office, published on 12 Apr 2017. 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: There is no known exploitation of CVE-2017-0197 in the wild and no public exploit code.

Affected product: Microsoft Corporation 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-2017-0197/ (Markdown: https://insights.sbomify.com/CVE-2017-0197/index.md)
```

## Sources

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

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