vciy

CVE-2017-0204

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 Outlook 2007 SP3, Microsoft Outlook 2010 SP2, Microsoft Outlook 2013 SP1, and Microsoft Outlook 2016 allow remote attackers to bypass the…

CVE-2017-02044 of 4 sources documented this
37

rank 37 = 18 + 14 + 0 + 5 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.19011  ·  without this subject the record ranks 19

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.5, from NVD  ·  without this subject the record ranks 23

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 37

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$581,000over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$581,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.19011 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.19011EPSSNOT IN KEVas of 2026-09-20
Severity5.5 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationpublic proof-of-conceptreceipt
Defenseno fix version held
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2025-03-17, 538 days at 0.19, 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 Outlook? 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 · no privileges required · user interaction required · low attack complexityreceipt
ImpactComplete integrity 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, 2017-04-13.

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

Authority who says so

CVSS, NVD5.5 MEDIUMreceipt
Exploit probability0.19011 · top 3% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes25 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Corporation Outlookreceipt
Published rangesmicrosoft outlook 2007; microsoft outlook 2010; microsoft outlook 2013; microsoft outlook 2016receipt

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 Outlook 2007 SP3, Microsoft Outlook 2010 SP2, Microsoft Outlook 2013 SP1, and Microsoft Outlook 2016 allow remote attackers to bypass the Office Protected View via a specially crafted document, aka "Microsoft Office Security Feature Bypass Vulnerability." receipt

NVD's analysis a second authority

severity
5.5 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
affected versions
microsoft outlook 2007; microsoft outlook 2010; microsoft outlook 2013; and 1 more, listed in full below

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

Dated events

2022-02-04EPSS moved 0.11 to 0.252023-03-07EPSS moved 0.25 to 0.002026-06-15EPSS moved 0.12 to 0.19

Movement the material steps

14 Apr 20210.10776
4 Feb 20220.2509
7 Mar 20230.00415 · crossed 0.10 · scoring model v2023.03.01
17 Mar 20250.10026 · crossed 0.10 · scoring model v2025.03.14
19 Mar 20250.24925
20 Mar 20250.10026
27 Mar 20250.24925
28 Mar 20250.11275
29 Mar 20250.24925
30 Mar 20250.11275
15 Jun 20260.19011 · scoring model v2026.06.15
6 Sep 20260.19011

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 22 observations
14 Apr 20210.10776
4 Feb 20220.2509
7 Mar 20230.00415
23 Mar 20230.00490
28 Apr 20230.00588
28 Aug 20230.00609
17 Dec 20240.02991
17 Mar 20250.10026
19 Mar 20250.24925
20 Mar 20250.10026
22 Mar 20250.11275
27 Mar 20250.24925
28 Mar 20250.11275
29 Mar 20250.24925
30 Mar 20250.11275
3 Jul 20250.12838
20 Oct 20250.11657
15 Jun 20260.19011
23 Aug 20260.1758
30 Aug 20260.19011
5 Sep 20260.1758
6 Sep 20260.19011

22 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.19011Published2017-04-12Public PoC2017-04-13Index as of2026-09-06

Exploit probability more than doubled between 2025-03-17 and 2025-03-19 (0.10026 → 0.24925) and the record had been public for 9 years, 4 months when this index was last written.

Published 2017-04-12 receipt · Public PoC 2017-04-13 receipt · Index as of 2026-09-06 derived

Siblings and hubs

Records related to this one

Browse the index from here

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

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.