BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2018
CVE-2018-8225High confidence

Microsoft Windows 7: security vulnerability

Microsoft · Windows 7

8.1HighCVSS 3.0
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 5 Oct 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 24.26% for the current model date.

Compensating controls

  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Microsoft Windows 7 and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  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 3 daysRemediation target: Within 90 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.

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-2018-19894

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 actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
01

What, why and how

A remote code execution vulnerability exists in Windows Domain Name System (DNS) DNSAPI.dll when it fails to properly handle DNS responses, aka "Windows DNSAPI Remote Code Execution Vulnerability." This affects Windows 7, Windows Server 2012 R2, Windows RT 8.1, Windows Server 2008, Windows Server 2012, Windows 8.1, Windows Server 2016, Windows Server 2008 R2, Windows 10, Windows 10 Servers.

What

A remote code execution vulnerability exists in Windows Domain Name System (DNS) DNSAPI.dll when it fails to properly handle DNS responses, aka "Windows DNSAPI Remote Code Execution Vulnerability." This affects Windows 7, Windows Server 2012 R2, Windows RT 8.1, Windows Server 2008, Windows Server 2012, Windows 8.1, Windows Server 2016, Windows Server 2008 R2, Windows 10, Windows 10 Servers.

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 a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

What

A remote code execution vulnerability exists in Windows Domain Name System (DNS) DNSAPI.dll when it fails to properly handle DNS responses, aka "Windows DNSAPI Remote Code Execution Vulnerability." This affects Windows 7, Windows Server 2012 R2, Windows RT 8.1, Windows Server 2008, Windows Server 2012, Windows 8.1, Windows Server 2016, Windows Server 2008 R2, Windows 10, Windows 10 Servers.

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 a network path 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
a network path → vulnerable operation → execute code or commands in the affected security context
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
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.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

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

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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.
NetworkUnauthenticatedRemote 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 · AV18-095Microsoft security updates

rer Microsoft Edge Microsoft Windows Microsoft Office and Microsoft Office Services and Web Apps ChakraCore Adobe Flash Player Microsoft guidance for CBC Symmetric Encryption Security Feature Bypass CVE References: CVE-2018-0871, CVE-2018-0978, CVE-2018-0982, CVE-2018-1036, CVE-2018-1040, CVE-2018-8110, CVE-2018-8111, CVE-2018-8113, CVE-2018-8121, CVE-2018-8140, CVE-2018-8169, CVE-2018-8175, CVE-2018-8201, CVE-2018-8205, CVE-2018-8207, CVE-2018-8208, CVE-2018-8209, CVE-2018-8210, CVE-2018-8211, CVE-2018-8212, CVE-2018-8213, CVE-2018-8214, CVE-2018-8215, CVE-2018-8216, CVE-2018-8217, CVE-2018-8218, CVE-2018-8219, CVE-2018-8221, CVE-2018-8224, CVE-2018-8225, CVE-2018-8226, CVE-2018-8227, CVE-2018-8229, CVE-2018-8231, CVE-2018-8233, CVE-2018-8234, CVE-2018-8235, CVE-2018-8236, CVE-2018-8239, CVE-2018-8243, CVE-2018-8244, CVE-2018-8245, CVE-2018-8246, CVE-2018-8247, CVE-2018-8248, CVE-2018-8249, CVE-2018-8251, CVE-2018-8252, CVE-2018-8254, CVE-2018-8267 Suggested Action CCIRC recommends that system administrators test and deploy the vendor-released updates to affected applications accordingly. References: https://portal.msrc.microsoft.com/en-us/security-guidance https://docs.microsoft.com/en-us/security-updates/securityadvisories/2018/4338110

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

.cve.org/CVERecord?id=CVE-2018-8213 Référence CVE CVE-2018-8214 https://www.cve.org/CVERecord?id=CVE-2018-8214 Référence CVE CVE-2018-8215 https://www.cve.org/CVERecord?id=CVE-2018-8215 Référence CVE CVE-2018-8216 https://www.cve.org/CVERecord?id=CVE-2018-8216 Référence CVE CVE-2018-8217 https://www.cve.org/CVERecord?id=CVE-2018-8217 Référence CVE CVE-2018-8218 https://www.cve.org/CVERecord?id=CVE-2018-8218 Référence CVE CVE-2018-8219 https://www.cve.org/CVERecord?id=CVE-2018-8219 Référence CVE CVE-2018-8221 https://www.cve.org/CVERecord?id=CVE-2018-8221 Référence CVE CVE-2018-8224 https://www.cve.org/CVERecord?id=CVE-2018-8224 Référence CVE CVE-2018-8225 https://www.cve.org/CVERecord?id=CVE-2018-8225 Référence CVE CVE-2018-8226 https://www.cve.org/CVERecord?id=CVE-2018-8226 Référence CVE CVE-2018-8231 https://www.cve.org/CVERecord?id=CVE-2018-8231 Référence CVE CVE-2018-8233 https://www.cve.org/CVERecord?id=CVE-2018-8233 Référence CVE CVE-2018-8239 https://www.cve.org/CVERecord?id=CVE-2018-8239 Référence CVE CVE-2018-8251 https://www.cve.org/CVERecord?id=CVE-2018-8251 Référence CVE CVE-2018-0982 https://www.cve.org/CVERecord?id=CVE-2018-0982 Référence CVE CVE-2018-1036 https://www.cve.org/CVERecord?id=CVE-2018-1036 Référence CVE CVE-2018-1040 https://www.cve.org/CVERecord?id=CVE-2018-1040 Ré

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2018-004946複数の Microsoft Windows 製品の Windows Domain Name System の DNSAPI.dll におけるリモートでコードを実行される脆弱性

複数の Microsoft Windows 製品の Windows Domain Name System (DNS) の DNSAPI.dll には、DNS レスポンスの適切な処理に失敗した場合、リモートでコードを実行される脆弱性が存在します。 ベンダは、本脆弱性を「Windows DNSAPI のリモートでコードが実行される脆弱性」として公開しています。

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

- 원격코드실행 취약점(CVE-2018-8110,CVE-2018-8111,CVE-2018-8175,CVE-2018-8210,CVE-2018-8213,CVE-2018-8225,CVE-2018-8227,CVE-2018-8229,CVE-2018-8231,CVE-2018-8236,CVE-2018-8251)

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 not verified
Affected
  • Windows 7: 32-bit Systems Service Pack 1, x64-based Systems Service Pack 1
  • Windows Server 2012 R2: (Server Core installation)
  • Windows RT 8.1: Windows RT 8.1
  • Windows Server 2008: 32-bit Systems Service Pack 2, 32-bit Systems Service Pack 2 (Server Core installation), Itanium-Based Systems Service Pack 2, x64-based Systems Service Pack 2, x64-based Systems Service Pack 2 (Server Core installation)
  • Windows Server 2012: (Server Core installation)
  • Windows 8.1: 32-bit systems, x64-based systems
  • Windows Server 2016: (Server Core installation)
  • Windows Server 2008 R2: Itanium-Based Systems Service Pack 1, x64-based Systems Service Pack 1, x64-based Systems Service Pack 1 (Server Core installation)
  • Windows 10: 32-bit Systems, Version 1607 for 32-bit Systems, Version 1607 for x64-based Systems, Version 1703 for 32-bit Systems, Version 1703 for x64-based Systems, Version 1709 for 32-bit Systems, Version 1709 for x64-based Systems, Version 1803 for 32-bit Systems, Version 1803 for x64-based Systems, x64-based Systems
  • Windows 10 Servers: version 1709 (Server Core Installation), version 1803 (Server Core Installation)
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 14 Jun 2018 · Last source change 5 Aug 2024, 06:46 UTC · CWE not yet assigned

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-01
European sourceENISA EUVD · EUVD-2018-19894
Product sourceCNA
Remediation sourceCVE/CNA references
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. ENISA EUVD mappingEUVD-2018-19894 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2018-19894"}
    ENISA EUVD ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: portal.msrc.microsoft.com/CVE-2018-8225.
    Before
    no authoritative guidance recorded
    After
    vendor advisory: portal.msrc.microsoft.com/CVE-2018-8225
    portal.msrc.microsoft.com ↗
  3. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    NIST NVD ↗
  4. CVSS scoreCVSS score changed from not recorded to 8.1 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).
    Before
    not recorded
    After
    8.1 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)
    NIST NVD ↗
  5. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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-2018-8225 · cve.blacktree.nl