# CVE-2015-1697: Code injection in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a crafted Journal file in Microsoft Windows.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 May 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gx8p-7jw3-phcx

## What is CVE-2015-1697?

CVE-2015-1697 is a critical code injection vulnerability in Microsoft Windows 7, published on 13 May 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1 allow remote attackers to execute arbitrary code via a crafted Journal file, aka "Windows Journal Remote Code Execution Vulnerability," a different vulnerability than CVE-2015-1675, CVE-2015-1695, CVE-2015-1696, CVE-2015-1698, and CVE-2015-1699.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2015-1697?

It affects 8 products.


Products: Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 8.1, Microsoft Windows Rt, Microsoft Windows Rt 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Vista.

## How do I fix CVE-2015-1697?

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

## Is CVE-2015-1697 being exploited?

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

## Other vulnerabilities in Microsoft Windows 7

- [CVE-2015-1635](https://insights.sbomify.com/CVE-2015-1635/): Microsoft HTTP.sys Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-2360](https://insights.sbomify.com/CVE-2015-2360/): Microsoft Win32k Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6324](https://insights.sbomify.com/CVE-2014-6324/): Microsoft Kerberos Key Distribution Center (KDC) Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6332](https://insights.sbomify.com/CVE-2014-6332/): Microsoft Windows Object Linking & Embedding (OLE) Automation Array Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2014-4148](https://insights.sbomify.com/CVE-2014-4148/): Microsoft Windows Remote Code Execution (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1697 and fix it if it is affected.

What it is: CVE-2015-1697 is a critical code injection vulnerability in Microsoft Windows 7, published on 13 May 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-1697 in the wild and no public exploit code.

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

## Sources

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

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