What is the severity of CVE-2005-3168?

CVE-2005-3168 is classified as a medium severity vulnerability due to its potential to allow less secure permissions on folders.

How do I fix CVE-2005-3168?

To fix CVE-2005-3168, you should apply Update Rollup 1 for SP4 for Microsoft Windows 2000.

Which software versions are affected by CVE-2005-3168?

CVE-2005-3168 affects Microsoft Windows 2000 running Service Pack 4 prior to Update Rollup 1.

What are the consequences of CVE-2005-3168?

The consequence of CVE-2005-3168 is that it could result in improperly applied Access Control Lists on certain folders, leading to inadequate security.

Is CVE-2005-3168 still relevant today?

CVE-2005-3168 is less relevant today as Microsoft Windows 2000 is no longer supported, but awareness of historical vulnerabilities is important for legacy systems.

Vulnerability/
CVE-2005-3168

high

7.5

CWE

NVD-CWE-Other

6/10/2005

3/10/2022

7/8/2024

CVE-2005-3168

First published: Thu Oct 06 2005(Updated: )

The SECEDIT command on Microsoft Windows 2000 before Update Rollup 1 for SP4, when using a security template to set Access Control Lists (ACLs) on folders, does not apply ACLs on folders that are listed after a long folder entry, which could result in less secure permissions than specified by the template.

Credit: cve@mitre.org

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

Remedy

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

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-3168?
CVE-2005-3168 is classified as a medium severity vulnerability due to its potential to allow less secure permissions on folders.
How do I fix CVE-2005-3168?
To fix CVE-2005-3168, you should apply Update Rollup 1 for SP4 for Microsoft Windows 2000.
Which software versions are affected by CVE-2005-3168?
CVE-2005-3168 affects Microsoft Windows 2000 running Service Pack 4 prior to Update Rollup 1.
What are the consequences of CVE-2005-3168?
The consequence of CVE-2005-3168 is that it could result in improperly applied Access Control Lists on certain folders, leading to inadequate security.
Is CVE-2005-3168 still relevant today?
CVE-2005-3168 is less relevant today as Microsoft Windows 2000 is no longer supported, but awareness of historical vulnerabilities is important for legacy systems.

collector/nvd-historical
collector/nvd-index
agent/references
agent/type
agent/first-publish-date
agent/remedy
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/weakness
agent/last-modified-date
agent/severity
agent/author
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-3168?
CVE-2005-3168 is classified as a medium severity vulnerability due to its potential to allow less secure permissions on folders.
How do I fix CVE-2005-3168?
To fix CVE-2005-3168, you should apply Update Rollup 1 for SP4 for Microsoft Windows 2000.
Which software versions are affected by CVE-2005-3168?
CVE-2005-3168 affects Microsoft Windows 2000 running Service Pack 4 prior to Update Rollup 1.
What are the consequences of CVE-2005-3168?
The consequence of CVE-2005-3168 is that it could result in improperly applied Access Control Lists on certain folders, leading to inadequate security.
Is CVE-2005-3168 still relevant today?
CVE-2005-3168 is less relevant today as Microsoft Windows 2000 is no longer supported, but awareness of historical vulnerabilities is important for legacy systems.