What is the severity of CVE-2002-1713?

CVE-2002-1713 is considered a low-severity vulnerability due to its impact being confined to local users.

How do I fix CVE-2002-1713?

To fix CVE-2002-1713, ensure that the permissions of home directories are set appropriately to prevent world-readable access.

Who is affected by CVE-2002-1713?

CVE-2002-1713 affects users of Mandrake Linux version 8.2 who have not modified the default security settings.

What could happen if CVE-2002-1713 is exploited?

If exploited, CVE-2002-1713 could allow local users to read the files of other users, leading to potential data leakage.

Is CVE-2002-1713 still relevant today?

CVE-2002-1713 may still be relevant for legacy systems running Mandrake Linux 8.2, though it is outdated and not commonly used.

Vulnerability/
CVE-2002-1713

medium

5.5

CWE

NVD-CWE-Other 276

31/12/2002

21/6/2005

8/8/2024

CVE-2002-1713

First published: Tue Dec 31 2002(Updated: )

The Standard security setting for Mandrake-Security package (msec) in Mandrake 8.2 installs home directories with world-readable permissions, which could allow local users to read other user's files.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Mandrake Linux	=8.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2002-1713?
CVE-2002-1713 is considered a low-severity vulnerability due to its impact being confined to local users.
How do I fix CVE-2002-1713?
To fix CVE-2002-1713, ensure that the permissions of home directories are set appropriately to prevent world-readable access.
Who is affected by CVE-2002-1713?
CVE-2002-1713 affects users of Mandrake Linux version 8.2 who have not modified the default security settings.
What could happen if CVE-2002-1713 is exploited?
If exploited, CVE-2002-1713 could allow local users to read the files of other users, leading to potential data leakage.
Is CVE-2002-1713 still relevant today?
CVE-2002-1713 may still be relevant for legacy systems running Mandrake Linux 8.2, though it is outdated and not commonly used.

agent/references
agent/type
agent/first-publish-date
agent/severity
agent/weakness
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/source
agent/tags
agent/softwarecombine
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
collector/nvd-historical
collector/nvd-index
agent/author
vendor/mandrakesoft
canonical/mandrake linux
version/mandrake linux/8.2

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-2002-1713?
CVE-2002-1713 is considered a low-severity vulnerability due to its impact being confined to local users.
How do I fix CVE-2002-1713?
To fix CVE-2002-1713, ensure that the permissions of home directories are set appropriately to prevent world-readable access.
Who is affected by CVE-2002-1713?
CVE-2002-1713 affects users of Mandrake Linux version 8.2 who have not modified the default security settings.
What could happen if CVE-2002-1713 is exploited?
If exploited, CVE-2002-1713 could allow local users to read the files of other users, leading to potential data leakage.
Is CVE-2002-1713 still relevant today?
CVE-2002-1713 may still be relevant for legacy systems running Mandrake Linux 8.2, though it is outdated and not commonly used.