CVE-2002-1924
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 · uneditedPowerChute plus 5.0.2 creates a "Pwrchute" directory during installation that is shared and world writeable, which could allow remote attackers to modify or create files in that directory.
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 confidencePowerChute Plus 5.0.2 creates a "Pwrchute" directory during installation that is configured with shared and world-writable permissions. This allows any local or remote attacker with access to the system to modify or create arbitrary files within that directory, potentially enabling privilege escalation or code execution.
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= 5.0.2CVSS 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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm PowerChute Plus installationCheck if PowerChute Plus version 5.0.2 is installed by looking for the program in Add/Remove Programs or searching for PowerChute-related files on the systemAffected if The software version matches 5.0.2
-
Locate the Pwrchute directorySearch the filesystem for a directory named 'Pwrchute'. Common locations include the Windows installation drive root (e.g., C:\Pwrchute) or Program Files directories. Use the command: dir /s /b C:\Pwrchute 2>nul or locate the directory through File Explorer searchAffected if A Pwrchute directory exists on the system
-
Inspect directory permissionsRight-click the Pwrchute folder, select Properties, then go to the Security tab. Examine the permissions for the 'Everyone' group or 'Users' group. Alternatively, use icacls command: icacls "C:\Pwrchute" (or actual path found)Affected if The Everyone group or World/Users permissions include Write or Full Control access, making the directory world-writable
The system is affected if PowerChute Plus 5.0.2 is installed and the Pwrchute directory exists with world-writable permissions allowing any user to write or modify files in that directory.
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 dataModify the Pwrchute directory permissions to remove world-writeable access, restricting write permissions to only the administrator or specific trusted users. Verify that any files created by the application use appropriate restrictive permissions.
- Consultation1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1924 — 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-1924 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