# CVE-2015-0008: Auth bypass in n/a

> Remote attackers can execute arbitrary code by exploiting missing server-to-client authentication in Windows UNC implementation via spoofed domain controllers.

- **Severity:** High 8.3 (`AV:A/AC:L/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:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6jrw-vwwr-mh3p

## What is CVE-2015-0008?

CVE-2015-0008 is a high-severity authentication bypass vulnerability in Microsoft Windows 7, published on 11 Feb 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The UNC implementation in Microsoft Windows Server 2003 SP2, 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 does not include authentication from the server to the client, which allows remote attackers to execute arbitrary code by making crafted data available on a UNC share, as demonstrated by Group Policy data from a spoofed domain controller, aka "Group Policy Remote Code Execution Vulnerability."

Weakness: CWE-284 (Improper Access Control)

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

It affects 9 products.


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

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

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

## Is CVE-2015-0008 being exploited?

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

Public exploit code:

- Microsoft Windows Server 2012 - 'Group Policy' Remote Code Execution (MS15-011) (exploitdb)

## 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-0008 and fix it if it is affected.

What it is: CVE-2015-0008 is a high-severity authentication bypass vulnerability in Microsoft Windows 7, published on 11 Feb 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-0008 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-0008/ (Markdown: https://insights.sbomify.com/CVE-2015-0008/index.md)
```

## Sources

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

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