# CVE-2017-11774: Microsoft Office Outlook Security Feature Bypass

> Attackers can execute arbitrary commands via memory handling flaws in Microsoft Outlook, bypassing security features.

- **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:** Yes, since 3 Nov 2021 (CISA KEV)
- **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:** 13 Oct 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-9cq3-gr97-qxf7

## What is CVE-2017-11774?

CVE-2017-11774 is a high-severity vulnerability in Microsoft Outlook, published on 13 Oct 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 Outlook 2010 SP2, Outlook 2013 SP1 and RT SP1, and Outlook 2016 allow an attacker to execute arbitrary commands, due to how Microsoft Office handles objects in memory, aka "Microsoft Outlook Security Feature Bypass Vulnerability."

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Microsoft Outlook.

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

No fix has been published for CVE-2017-11774 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2017-11774 being exploited?

Yes. Attackers have exploited CVE-2017-11774 in the wild since at least 3 Nov 2021.

Public exploit code:

- used to generate a valid attack chain to exploit CVE-2017-11774 tied to iranian apt only reasearch poc dont use for harm please (github_poc): https://github.com/devcoinfet/SniperRoost

## Other vulnerabilities in Microsoft Outlook

- [CVE-2001-0538](https://insights.sbomify.com/CVE-2001-0538/): Code injection in n/a (critical 10.0)
- [CVE-2013-3870](https://insights.sbomify.com/CVE-2013-3870/): Use after free in n/a (critical 9.3)
- [CVE-2010-2728](https://insights.sbomify.com/CVE-2010-2728/): Memory corruption in n/a (critical 9.3)
- [CVE-2010-0266](https://insights.sbomify.com/CVE-2010-0266/): Code injection in n/a (critical 9.3)
- [CVE-2003-1378](https://insights.sbomify.com/CVE-2003-1378/): Code injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11774 is a high-severity vulnerability in Microsoft Outlook, published on 13 Oct 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: Yes. Attackers have exploited CVE-2017-11774 in the wild since at least 3 Nov 2021.

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

## Sources

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

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