What is the severity of CVE-2001-0859?

CVE-2001-0859 is considered a high-severity vulnerability due to its potential to allow unauthorized users to modify or delete files.

How do I fix CVE-2001-0859?

To fix CVE-2001-0859, you should update the kernel to a patched version that addresses the default umask for init.

What impact does CVE-2001-0859 have on my system?

CVE-2001-0859 can lead to security risks by allowing files to be created with world-writable permissions, enabling unauthorized access.

Which systems are affected by CVE-2001-0859?

CVE-2001-0859 affects Red Hat Linux version 7.1, specifically the 2.4.3-12 kernel.

What is the cause of the vulnerability described in CVE-2001-0859?

The vulnerability in CVE-2001-0859 is caused by the kernel's init process setting the default umask to 000, allowing files to be created with insecure permissions.

Vulnerability/
CVE-2001-0859

medium

CWE

NVD-CWE-Other

6/12/2001

9/3/2002

8/8/2024

CVE-2001-0859

First published: Thu Dec 06 2001(Updated: )

2.4.3-12 kernel in Red Hat Linux 7.1 Korean installation program sets the setting default umask for init to 000, which installs files with world-writeable permissions.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Red Hat Linux	=7.1

Remedy

http://www.redhat.com/support/errata/RHSA-2001-148.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2001-0859?
CVE-2001-0859 is considered a high-severity vulnerability due to its potential to allow unauthorized users to modify or delete files.
How do I fix CVE-2001-0859?
To fix CVE-2001-0859, you should update the kernel to a patched version that addresses the default umask for init.
What impact does CVE-2001-0859 have on my system?
CVE-2001-0859 can lead to security risks by allowing files to be created with world-writable permissions, enabling unauthorized access.
Which systems are affected by CVE-2001-0859?
CVE-2001-0859 affects Red Hat Linux version 7.1, specifically the 2.4.3-12 kernel.
What is the cause of the vulnerability described in CVE-2001-0859?
The vulnerability in CVE-2001-0859 is caused by the kernel's init process setting the default umask to 000, allowing files to be created with insecure permissions.

agent/references
agent/type
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/remedy
agent/last-modified-date
agent/weakness
agent/author
agent/severity
agent/event
agent/description
agent/source
agent/softwarecombine
agent/tags
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
vendor/redhat
canonical/red hat linux
version/red hat linux/7.1

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-2001-0859?
CVE-2001-0859 is considered a high-severity vulnerability due to its potential to allow unauthorized users to modify or delete files.
How do I fix CVE-2001-0859?
To fix CVE-2001-0859, you should update the kernel to a patched version that addresses the default umask for init.
What impact does CVE-2001-0859 have on my system?
CVE-2001-0859 can lead to security risks by allowing files to be created with world-writable permissions, enabling unauthorized access.
Which systems are affected by CVE-2001-0859?
CVE-2001-0859 affects Red Hat Linux version 7.1, specifically the 2.4.3-12 kernel.
What is the cause of the vulnerability described in CVE-2001-0859?
The vulnerability in CVE-2001-0859 is caused by the kernel's init process setting the default umask to 000, allowing files to be created with insecure permissions.