What is the severity of CVE-2005-3171?

CVE-2005-3171 is considered to have a moderate severity level due to its potential impact on system administration and the incorrect indication of Group Policy updates.

How do I fix CVE-2005-3171?

To fix CVE-2005-3171, ensure that your system is updated with Update Rollup 1 for Windows 2000 Service Pack 4.

What systems are affected by CVE-2005-3171?

CVE-2005-3171 affects Microsoft Windows 2000 systems that are running Service Pack 4.

What are the consequences of CVE-2005-3171?

The consequence of CVE-2005-3171 is that system administrators may mistakenly believe that Group Policy settings have been successfully applied when, in fact, they have not.

Is there a workaround for CVE-2005-3171?

There are no specific workarounds for CVE-2005-3171 besides applying the necessary updates and patches from Microsoft.

Vulnerability/
CVE-2005-3171

medium

4.6

CWE

NVD-CWE-Other

6/10/2005

3/10/2022

7/8/2024

CVE-2005-3171

First published: Thu Oct 06 2005(Updated: )

Microsoft Windows 2000 before Update Rollup 1 for SP4 records Event ID 1704 to indicate that Group Policy security settings were successfully updated, even when the processing fails such as when Ntuser.pol cannot be accessed, which could cause system administrators to believe that the system is compliant with the specified settings.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Microsoft Windows 2000	=sp4

Remedy

http://support.microsoft.com/kb/884559

Remedy

http://support.microsoft.com/kb/900345

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2005-3171?
CVE-2005-3171 is considered to have a moderate severity level due to its potential impact on system administration and the incorrect indication of Group Policy updates.
How do I fix CVE-2005-3171?
To fix CVE-2005-3171, ensure that your system is updated with Update Rollup 1 for Windows 2000 Service Pack 4.
What systems are affected by CVE-2005-3171?
CVE-2005-3171 affects Microsoft Windows 2000 systems that are running Service Pack 4.
What are the consequences of CVE-2005-3171?
The consequence of CVE-2005-3171 is that system administrators may mistakenly believe that Group Policy settings have been successfully applied when, in fact, they have not.
Is there a workaround for CVE-2005-3171?
There are no specific workarounds for CVE-2005-3171 besides applying the necessary updates and patches from Microsoft.

collector/nvd-historical
collector/nvd-index
agent/references
agent/type
agent/softwarecombine
agent/first-publish-date
agent/remedy
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/author
agent/weakness
agent/tags
agent/description
agent/event
agent/source
vendor/microsoft
canonical/microsoft windows 2000
version/microsoft windows 2000/sp4

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2005-3171?
CVE-2005-3171 is considered to have a moderate severity level due to its potential impact on system administration and the incorrect indication of Group Policy updates.
How do I fix CVE-2005-3171?
To fix CVE-2005-3171, ensure that your system is updated with Update Rollup 1 for Windows 2000 Service Pack 4.
What systems are affected by CVE-2005-3171?
CVE-2005-3171 affects Microsoft Windows 2000 systems that are running Service Pack 4.
What are the consequences of CVE-2005-3171?
The consequence of CVE-2005-3171 is that system administrators may mistakenly believe that Group Policy settings have been successfully applied when, in fact, they have not.
Is there a workaround for CVE-2005-3171?
There are no specific workarounds for CVE-2005-3171 besides applying the necessary updates and patches from Microsoft.