BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2020
CVE-2020-16898High confidence

Windows TCP/IP Remote Code Execution Vulnerability

Microsoft · Windows 10 Version 1803

8.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 10.94% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Microsoft Windows 10 Version 1803 and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
SCA-2020-0005 · CSAF 2.0 · revision 3 · finalSICK PSIRTPackage Analytics affected by Windows TCP/IP vulnerability
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SICK Package Analytics 4.0 up to 4.1.2
Summary
A remote code execution vulnerability exists when the Windows TCP/IP stack improperly handles ICMPv6 Router Advertisement packets, aka 'Windows TCP/IP Remote Code Execution Vulnerability'.
Remediation
This issue is addressed in the Microsoft update for CVE-2020-16898.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2020-8856

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

<p>A remote code execution vulnerability exists when the Windows TCP/IP stack improperly handles ICMPv6 Router Advertisement packets. An attacker who successfully exploited this vulnerability could gain the ability to execute code on the target server or client.</p> <p>To exploit this vulnerability, an attacker would have to send specially crafted ICMPv6 Router Advertisement packets to a remote Windows computer.</p> <p>The update addresses the vulnerability by correcting how the Windows TCP/IP stack handles ICMPv6 Router Advertisement packets.</p>

What

<p>A remote code execution vulnerability exists when the Windows TCP/IP stack improperly handles ICMPv6 Router Advertisement packets. An attacker who successfully exploited this vulnerability could gain the ability to execute code on the target server or client.</p> <p>To exploit this vulnerability, an attacker would have to send specially crafted ICMPv6 Router Advertisement packets to a remote Windows computer.</p> <p>The update addresses the vulnerability by correcting how the Windows TCP/IP stack handles ICMPv6 Router Advertisement packets.</p>

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

What

<p>A remote code execution vulnerability exists when the Windows TCP/IP stack improperly handles ICMPv6 Router Advertisement packets. An attacker who successfully exploited this vulnerability could gain the ability to execute code on the target server or client.</p> <p>To exploit this vulnerability, an attacker would have to send specially crafted ICMPv6 Router Advertisement packets to a remote Windows computer.</p> <p>The update addresses the vulnerability by correcting how the Windows TCP/IP stack handles ICMPv6 Router Advertisement packets.</p>

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
an adjacent network → vulnerable operation → execute code or commands in the affected security context
Attack surface
Adjacent
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
UnauthenticatedRemote code execution
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Canadian Centre for Cyber Security · English · AV20-369Microsoft security advisory – October 2020 monthly rollup

On 13 October 2020 Microsoft published Security Updates to address vulnerabilities in multiple products. Included were critical severity patches for the following: Of note is a remote code execution vulnerability, tracked as CVE-2020-16898 which exists when the Windows TCP/IP stack improperly handles ICMPv6 Router Advertisement packets. An actor who successfully exploits this vulnerability could gain the ability to execute code on the target server or client. Microsoft has published updates which address the vulnerability by correcting how the Windows TCP/IP stack handles ICMPv6 Router Advertisement packets.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20201021Security Bulletin 21 Oct 2020

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 21 Oct 2020, published on 21 October 2020. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2020-AVI-634Multiples vulnérabilités dans Microsoft Windows

d?id=CVE-2020-16887 Référence CVE CVE-2020-16889 https://www.cve.org/CVERecord?id=CVE-2020-16889 Référence CVE CVE-2020-16890 https://www.cve.org/CVERecord?id=CVE-2020-16890 Référence CVE CVE-2020-16891 https://www.cve.org/CVERecord?id=CVE-2020-16891 Référence CVE CVE-2020-16892 https://www.cve.org/CVERecord?id=CVE-2020-16892 Référence CVE CVE-2020-16894 https://www.cve.org/CVERecord?id=CVE-2020-16894 Référence CVE CVE-2020-16895 https://www.cve.org/CVERecord?id=CVE-2020-16895 Référence CVE CVE-2020-16896 https://www.cve.org/CVERecord?id=CVE-2020-16896 Référence CVE CVE-2020-16897 https://www.cve.org/CVERecord?id=CVE-2020-16897 Référence CVE CVE-2020-16898 https://www.cve.org/CVERecord?id=CVE-2020-16898 Référence CVE CVE-2020-16899 https://www.cve.org/CVERecord?id=CVE-2020-16899 Référence CVE CVE-2020-16900 https://www.cve.org/CVERecord?id=CVE-2020-16900 Référence CVE CVE-2020-16901 https://www.cve.org/CVERecord?id=CVE-2020-16901 Référence CVE CVE-2020-16902 https://www.cve.org/CVERecord?id=CVE-2020-16902 Référence CVE CVE-2020-16905 https://www.cve.org/CVERecord?id=CVE-2020-16905 Référence CVE CVE-2020-16907 https://www.cve.org/CVERecord?id=CVE-2020-16907 Référence CVE CVE-2020-16908 https://www.cve.org/CVERecord?id=CVE-2020-16908 Référence CVE CVE-2020-16909 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2020-010026Microsoft Windows 10 および Windows Server におけるリモートでコードを実行される脆弱性

Microsoft Windows 10 および Windows Server には、Windows TCP/IP スタックが ICMPv6 ルータアドバタイズパケットを適切に処理しない場合、リモートでコードを実行される脆弱性が存在します。 ベンダは、本脆弱性を「Windows TCP/IP のリモートでコードが実行される脆弱性」として公開しています。

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-5208MS 10월 보안 위협에 따른 정기 보안 업데이트 권고

- 원격코드실행 취약점(CVE-2020-1167, CVE-2020-16891, CVE-2020-16894, CVE-2020-16898, CVE-2020-16911, CVE-2020-16915, CVE-2020-16923, CVE-2020-16924, CVE-2020-16967, CVE-2020-16968)

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
SICK Package Analytics 4.0 up to 4.1.2
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 16 Oct 2020 · Last source change 4 Aug 2024, 13:45 UTC · CWE not yet assigned

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2020-8856
Product sourceVendor CSAF · SICK PSIRT
Remediation sourceVendor CSAF · SICK PSIRT
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added remediation: sick.com/special_information_sick_operating_guidelines_cybersecurity_by_sick_en_im0106719.pdf; removed remediation: portal.msrc.microsoft.com/CVE-2020-16898.
    Before
    remediation: portal.msrc.microsoft.com/CVE-2020-16898
    After
    remediation: sick.com/special_information_sick_operating_guidelines_cybersecurity_by_sick_en_im0106719.pdf
    SICK PSIRT ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2020-8856↗Vendor CSAF · SICK PSIRT↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2020-16898 · cve.blacktree.nl