SecPod

Learn Search

Search across all Learn content

← Back to Security Research
How to Fully Fix CVE-2017-8529, Microsoft Browser Information Disclosure Vulnerability

How to Fully Fix CVE-2017-8529, Microsoft Browser Information Disclosure Vulnerability

Microsoft has re-released a patch for CVE-2017-8529 to fix a print issue related to this vulnerability. The patch is not fully applied unless certain registry keys are set even after installing the respective Operating System patches. This article describes the steps to update registry settings to b...

Oct 16, 2018By Ashwitha Kallalike3 min read

Overview

Microsoft has re-released a patch for CVE-2017-8529 to fix a print issue related to this vulnerability. The patch is not fully applied unless certain registry keys are set even after installing the respective Operating System patches. This article describes the steps to update registry settings to be fully protected from CVE-2017-8529.  A vulnerability management software can detect these vulnerabilities and keep your security posture secure.

Affected OS

All supported Microsoft Windows except Windows 10 1709 and Windows 10 1803 are affected by CVE-2017-8529.

Solution for CVE-2017-8529

1. Install the patches recommended in the Microsoft advisory CVE-2017-8529.

2. Create the following registry entries.These attacks can be prevented by using a sound vulnerability management tool.

Here are the Steps to Update Your Registry Settings

By following these steps you can avoid vulnerabilities such as CVE-2017-8529 in the future.

For 32-bit and 64-bit systems:

  1. Click Start, click Run, type regedt32 or type regedit, and then click OK.
  2. In Registry Editor, locate the following registry path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\
  3. Right-click FeatureControl, point to New, and then click Key.
  4. Type FEATURE_ENABLE_PRINT_INFO_DISCLOSURE_FIX, and then press Enter to name the new subkey.
  5. Right-click FEATURE_ENABLE_PRINT_INFO_DISCLOSURE_FIX, point to New, and then click DWORD Value.
  6. Type “iexplore.exe” for the new DWORD value.
  7. Double-click the new DWORD value named iexplore.exe and change the Value data field to 1.
  8. Click OK to close.

For 64-bit systems only:

  1. Click Start, click Run, type regedt32 or type regedit, and then click OK.
  2. In Registry Editor, locate the following registry path: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Internet Explorer\Main\FeatureControl\
  3. Right-click FeatureControl, point to New, and then click Key.
  4. Type FEATURE_ENABLE_PRINT_INFO_DISCLOSURE_FIX, and then press Enter to name the new subkey.
  5. Right-click FEATURE_ENABLE_PRINT_INFO_DISCLOSURE_FIX, point to New, and then click DWORD Value.
  6. Type “iexplore.exe” for the new DWORD value.
  7. Double-click the new DWORD value named iexplore.exe and change the Value data field to 1.
  8. Click OK to close.

CVE-2017-8529 can be prevented by updating these registry settings.

Please refer to the below image for registry changes:

CVE-2017-8529 - print regression
CVE-2017-8529 - print regression

Automate Patching with SanerNow:

CVE-2017-8529 can be prevented by utilizing patch automation. Saner can automate the above patching across the organization with ease. Click here to explore patching steps using Saner.

SanerNow Personal Users:

Follow the below steps to patch the vulnerability CVE-2017-8529 fully:

1. Download the sp_cve-2017-8529_print_info_dis_reg_fix.zip zip file and unzip to get sp_cve-2017-8529_print_info_dis_reg_fix.exe2. Open the cmd.exe as an ‘administrator’3. Go to the path where sp_cve-2017-8529_print_info_dis_reg_fix.exe is extracted4. Run the below command with “/S” silent option to patch this vulnerability fully.C:\>sp_cve-2017-8529_print_info_dis_reg_fix.exe /S

By running this command CVE-2017-8529 can become less of a hassle.

These steps will resolve this vulnerability completely. SanerNow Advanced Vulnerability Management will stop reporting this vulnerability from the following manual or scheduled scan.

Have any questions on how to fix CVE-2017-8529 specific to your IT? Let’s discuss.

JOIN SECPOD COMMUNITY

Featured Posts

Open CVE-2023-49105: The ownCloud Authentication Flaw That Exposed Sensitive Credentials
CVE-2023-49105: The ownCloud Authentication Flaw That Exposed Sensitive Credentials

CVE Research

CVE-2023-49105: The ownCloud Authentication Flaw That Exposed Sensitive Credentials

Sep 25, 2026

Open Patch Analysis & Exploitation Timeline: RouterOS SSH Attacks Predate Production Fixes in CISA's September 10, 2026 KEV Additions
Patch Analysis & Exploitation Timeline: RouterOS SSH Attacks Predate Production Fixes in CISA's September 10, 2026 KEV Additions

CVE Research

Patch Analysis & Exploitation Timeline: RouterOS SSH Attacks Predate Production Fixes in CISA's September 10, 2026 KEV Additions

Two MikroTik RouterOS CVEs entered CISA KEV seven days after production fixes. Dated reporting places SSH-chain exploitation involving CVE-2026-86060 at least one calendar day before those releases; no comparable start date is established for CVE-2026-67277.

Sep 25, 2026

Open Patch Analysis & Exploitation Timeline: A Day-Old Chrome Bug and an Eight-Month-Old Fortinet Flaw Share the Same KEV Batch
Patch Analysis & Exploitation Timeline: A Day-Old Chrome Bug and an Eight-Month-Old Fortinet Flaw Share the Same KEV Batch

CVE Research

Patch Analysis & Exploitation Timeline: A Day-Old Chrome Bug and an Eight-Month-Old Fortinet Flaw Share the Same KEV Batch

Four vulnerabilities added to CISA’s KEV catalog on September 9, 2026 show widely different timelines between public disclosure and formal exploitation-based prioritization, ranging from one day to 239 days.

Sep 24, 2026

Open TA412/APT31: Mapping Threat Actor Patterns to CVE Exploitation Chains

TA412/APT31: Mapping Threat Actor Patterns to CVE Exploitation Chains

CVE Research

TA412/APT31: Mapping Threat Actor Patterns to CVE Exploitation Chains

A chronological look at how a long-running China-nexus espionage cluster evolved from server-side exploitation to a chained Chrome/Windows zero-day kit — and what that shift signals.

Sep 24, 2026