CVE-2002-1844
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 · uneditedMicrosoft Windows Media Player (WMP) 6.3, when installed on Solaris, installs executables with world-writable permissions, which allows local users to delete or modify the executables to gain privileges.
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 confidenceMicrosoft Windows Media Player 6.3 for Solaris installs executable files with world-writable permissions (chmod 777), allowing any local user on the system to modify or replace these binaries. A local attacker can exploit this to escalate privileges by replacing the WMP executables with malicious code.
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= 6.3CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WMP 6.3 is installed on SolarisSearch for Windows Media Player installation directories or executables on the Solaris system using 'find' or 'locate' commands to locate WMP-related filesAffected if Windows Media Player 6.3 is found installed on the Solaris system
-
Verify the exact version is 6.3Check the version information of the installed WMP executables using 'pkginfo', 'pkgparam', or by examining version strings within the binary filesAffected if The installed version is exactly 6.3 (version 6.3 only)
-
Identify WMP executable filesLocate all executable files associated with Windows Media Player installation, typically found in /opt, /usr/local, or the installation directoryAffected if WMP executable files exist on the system
-
Check file permissions are world-writableUse 'ls -la' command on the WMP executable files to inspect their permissions. Look for permissions showing 'rwxrwxrwx' (777) which indicates world-writable statusAffected if The WMP executable files have world-writable permissions (chmod 777)
-
Verify any user can modify the binariesTest write access to the WMP executables using a non-root account or check file ownership and permissions to confirm all users have write accessAffected if Non-privileged users can write to or modify the WMP executable files
A user is affected if they are running Microsoft Windows Media Player version 6.3 on Solaris with executable files set to world-writable (chmod 777) permissions, allowing any local user to modify the binaries.
Generated from the published advisory. Verify against your own configuration.
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 dataChange file permissions on WMP executables to remove world-writable access (chmod 755 or more restrictive), or uninstall WMP 6.3 from Solaris if not required.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1844 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2002-1844 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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