# CVE-2002-1924: Misconfiguration in n/a

> Remote attackers can modify or create files in the world-writable Pwrchute directory due to insecure default permissions.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6gm3-644h-2mm9

## What is CVE-2002-1924?

CVE-2002-1924 is a medium-severity vulnerability in n/a, published on 28 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PowerChute 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.

## Which versions are affected by CVE-2002-1924?

It affects 1 product.


Products: Apc Powerchute.

## How do I fix CVE-2002-1924?

No fix has been published for CVE-2002-1924 yet. Limit exposure of the affected software until one is available.

## Is CVE-2002-1924 being exploited?

There is no known exploitation of CVE-2002-1924 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2000-1242](https://insights.sbomify.com/CVE-2000-1242/): Hardcoded credentials in n/a (critical 9.0)
- [CVE-2020-7526](https://insights.sbomify.com/CVE-2020-7526/): Code injection in PowerChute Business Edition software V9.0.x and earlier (high 8.8)
- [CVE-2004-2046](https://insights.sbomify.com/CVE-2004-2046/): Denial of service in n/a (medium 5.0)
- [CVE-2011-4263](https://insights.sbomify.com/CVE-2011-4263/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1924 and fix it if it is affected.

What it is: CVE-2002-1924 is a medium-severity vulnerability in n/a, published on 28 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-1924 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2002-1924/ (Markdown: https://insights.sbomify.com/CVE-2002-1924/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2002-1924
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2002-1924
- OSV: https://osv.dev/vulnerability/CVE-2002-1924

---
From sbomify Insights: https://insights.sbomify.com/CVE-2002-1924/
Summaries are generated and may contain mistakes; the official description above is the record.