dbcve.org
Mandrake LinuxOperating system · Mandrakesoft

CVE-2002-1713

MEDIUM · 5.5 CVSS v3.1 Published 2002-12-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Mandrake-Security package (msec) in Mandrake Linux 8.2 configured home directories with world-readable permissions as its default security setting, allowing any local user to read sensitive files in other users' home directories.

MitigationChange home directory permissions to 750 or stricter (drwx-r-x---) and ensure umask is set to 077 for new user creations to prevent world-readable access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mandrake LinuxOperating system
Affected:= 8.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed operating system
    Run 'cat /etc/mandrake-release' or 'lsb_release -a' to confirm the OS is Mandrake Linux 8.2
    Affected if The OS is not Mandrake Linux 8.2, this specific CVE does not apply
  2. Check if msec package is installed
    Run 'rpm -q msec' or 'rpm -qa | grep msec' to see if the Mandrake-Security package is present
    Affected if The msec package is not installed, the vulnerability is not present
  3. Inspect home directory permissions
    Run 'ls -la /home/' and check the permissions on user home directories (the first field, e.g., 'drwxr-xr-x')
    Affected if Home directories have world-readable permissions (e.g., 'drwxr-xr-x' or 'rwxr-xr-x'), meaning others can read contents
  4. Check for the default umask setting
    Check /etc/profile, /etc/bashrc, or /etc/login.defs for the default umask value (look for lines containing 'umask')
    Affected if umask is set to 000 or another value that results in world-readable permissions (such as 022, which creates 755)

A system is affected only if it is Mandrake Linux 8.2 with the msec package installed and home directories have world-readable (755 or similar) permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Change home directory permissions to 750 or stricter (drwx-r-x---) and ensure umask is set to 077 for new user creations to prevent world-readable access.

Fix this in Mandrake Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-1713 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2002-1713 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data