vciy

CVE-2017-11783

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Microsoft Windows 8.1, Windows Server 2012 R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allows an elevation of…

CVE-2017-117834 of 4 sources documented this
38

rank 38 = 15 + 18 + 0 + 5 + 0

rank@v1 · scheduled

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.02501  ·  without this subject the record ranks 23

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.0, from NVD  ·  without this subject the record ranks 20

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 38

How much of the world it touches

NVD CPE configurations

4 products in the CPE ranges  ·  without this subject the record ranks 33

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 38

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$125,000over the next 30 days, if this record is yours
Movement-$1.42Mon 2022-02-04, the last material move, 4 years, 7 months before this reading
Basisassumeda published average, not your estate

$125,000 = $4.99M incident cost x 1 exposure x 0.02501 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.02501EPSSNOT IN KEVas of 2026-09-20
Severity7 HIGHreceipt
Harmtotal lossreceipt
Exploitationpublic proof-of-conceptreceipt
Defenseno fix version held
Movementfallenreceipt
PLATEAU10Minimal movement since 2022-02-04, 1675 days at 0.03, as of 2026-09-06. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running Microsoft Corporation Windows? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachneeds local access · low privileges required · no user interaction · high attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.0 · NVD's vectorreceipt
Weakness classNo CWE mapping in held sources.

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inNo fix version in held sources, as the index stood on 6 Sep 2026.
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Proof-of-concept published · 1 public repository, 2018-08-31.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 1 public repository2018-08-31receipt
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD7 HIGHreceipt
Exploit probability0.02501 · top 16% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes32 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Corporation Windowsreceipt
Published rangesmicrosoft windows 10 1511; microsoft windows 10 1607; microsoft windows 10 1703; microsoft windows server 2012 r2receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Microsoft Windows 8.1, Windows Server 2012 R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allows an elevation of privilege vulnerability in the way it handles calls to Advanced Local Procedure Call (ALPC), aka "Windows Elevation of Privilege Vulnerability". receipt

NVD's analysis a second authority

severity
7 CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
affected versions
microsoft windows 10 1511; microsoft windows 10 1607; microsoft windows 10 1703; and 1 more, listed in full below

check it yourself securitytracker.com portal.msrc.microsoft.com securityfocus.com receipt

Movement the material steps

14 Apr 20210.30098
4 Feb 20220.0169 · crossed 0.10
7 Mar 20237.9e-4 · scoring model v2023.03.01
17 Mar 20250.05461 · scoring model v2025.03.14
15 Jun 20260.02501 · scoring model v2026.06.15
6 Sep 20260.02501
Show all 29 observations
14 Apr 20210.30098
4 Feb 20220.0169
7 Mar 20237.9e-4
8 Mar 20230.00079
23 Aug 20230.00060
23 Sep 20230.00059
31 Jul 20240.00051
10 Aug 20240.00061
13 Aug 20240.00051
12 Sep 20240.00048
25 Oct 20240.00056
5 Dec 20240.00048
17 Dec 20240.00628
17 Mar 20250.05461
19 Mar 20250.05761
20 Mar 20250.05461
27 Mar 20250.05761
28 Mar 20250.08353
29 Mar 20250.05761
30 Mar 20250.08353
31 Mar 20250.07278
5 Jul 20250.07572
17 Mar 20260.07627
18 Mar 20260.03609
15 Jun 20260.02501
23 Aug 20260.03363
30 Aug 20260.02501
5 Sep 20260.03363
6 Sep 20260.02501

29 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.02501Published2017-10-13Public PoC2018-08-31Index as of2026-09-06

The record had been public for 8 years, 10 months when this index was last written.

Published 2017-10-13 receipt · Public PoC 2018-08-31 receipt · Index as of 2026-09-06 derived

Siblings and hubs

Records related to this one

Its defect family

microsoft corporation windows

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: computed, pro@dim2000

Nothing we hold separates this record from the others in its defect family. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2017-11783.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.