How severe is CVE-2017-0004?

No CVSS score has been assigned to CVE-2017-0004 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2017-0004?

Affected package information for CVE-2017-0004 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2017-0004?

No fixed release is recorded for CVE-2017-0004 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2017-0004 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2017-0004 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2017-0004 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-0004 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2017-0004?

CVE-2017-0004 has an EPSS (Exploit Prediction Scoring System) score of 91.4%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2017-0004?

CVE-2017-0004 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-0004 published, and has it been updated?

CVE-2017-0004 was published on January 10, 2017 and was last updated on August 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2017-0004 — Microsoft

CVE-2017-0004 is a Improper Input Validation vulnerability. EPSS puts its 30-day exploitation probability at 91.4% (100th percentile). No vendor fix is recorded yet; mitigation options are listed below.

The Local Security Authority Subsystem Service (LSASS) in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, and Windows 7 SP1 allows remote attackers to cause a denial…

Published

Jan 10, 2017

Updated

Aug 5, 2024

Affected

3 products

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

91.4%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

The Local Security Authority Subsystem Service (LSASS) in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, and Windows 7 SP1 allows remote attackers to cause a denial of service (reboot) via a crafted authentication request, aka "Local Security Authority Subsystem Service Denial of Service Vulnerability."

Affected Products

3 products · 4 configurations

windows 7microsoft

all

windows server 2008microsoft

1 version

windows vistamicrosoft

all

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2017-0004 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-0004 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works