# CVE-2002-1256: Security feature bypass in n/a

> Attackers can bypass SMB signing to inject malicious data into sessions, potentially modifying group policy information from domain controllers.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-vh5c-q7x4-mjrx

## What is CVE-2002-1256?

CVE-2002-1256 is a medium-severity vulnerability in Microsoft Windows 2000, published on 1 Sep 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SMB signing capability in the Server Message Block (SMB) protocol in Microsoft Windows 2000 and Windows XP allows attackers to disable the digital signing settings in an SMB session to force the data to be sent unsigned, then inject data into the session without detection, e.g. by modifying group policy information sent from a domain controller.

## Which versions are affected by CVE-2002-1256?

It affects 3 products.


Products: Microsoft Windows 2000, Microsoft Windows 2000 Terminal Services, Microsoft Windows Xp.

## How do I fix CVE-2002-1256?

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

## Is CVE-2002-1256 being exploited?

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

## Other vulnerabilities in Microsoft Windows 2000

- [CVE-2008-4250](https://insights.sbomify.com/CVE-2008-4250/): Microsoft Windows Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2010-0232](https://insights.sbomify.com/CVE-2010-0232/): Microsoft Windows Kernel Exception Handler (high 7.8, exploited in the wild)
- [CVE-2009-1123](https://insights.sbomify.com/CVE-2009-1123/): Microsoft Windows Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2002-0367](https://insights.sbomify.com/CVE-2002-0367/): Microsoft Windows Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2010-0269](https://insights.sbomify.com/CVE-2010-0269/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1256 and fix it if it is affected.

What it is: CVE-2002-1256 is a medium-severity vulnerability in Microsoft Windows 2000, published on 1 Sep 2004. 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-2002-1256 in the wild and no public exploit code.

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

## Sources

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

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