Menu

Star on GitHub · 3.2k

CVE-2017-11852

4.7 · MEDIUM

Microsoft GDI Component in Windows 7 SP1 and Windows Server 2008 SP2 and R2 SP1 allows an attacker to log on to an affected system and run a specially crafted application to compromise the user's s…

Published Nov 15, 2017CWE-200EPSS 2.20%

Overview

CVE-2017-11852 is a medium-severity vulnerability. It was published on November 15, 2017 and has a CVSS 3.0 base score of 4.7 (MEDIUM).

This vulnerability has a CVSS 3.0 base score of 4.7, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

Microsoft GDI Component in Windows 7 SP1 and Windows Server 2008 SP2 and R2 SP1 allows an attacker to log on to an affected system and run a specially crafted application to compromise the user's system, due improperly disclosing kernel memory addresses, aka "Windows GDI Information Disclosure Vulnerability".

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2017-11852?

CVE-2017-11852 is a medium-severity vulnerability. It was published on November 15, 2017 and has a CVSS 3.0 base score of 4.7 (MEDIUM).

How severe is CVE-2017-11852?

This vulnerability has a CVSS 3.0 base score of 4.7, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2017-11852?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2017-11852?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2017-11852 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2017

View all