# CVE-2002-1869: Denial of service in n/a

> Attackers can prevent event logging by locking the log file, causing a denial of service for audit trails in Heysoft EventSave.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Jun 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-45mq-v9rr-g7gg

## What is CVE-2002-1869?

CVE-2002-1869 is a low-severity denial of service vulnerability in n/a, published on 28 Jun 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Heysoft EventSave 5.1 and 5.2 and Heysoft EventSave+ 5.1 and 5.2 does not check whether the log file can be written to, which allows attackers to prevent events from being recorded by opening the log file using an application such as Microsoft's Event Viewer.

Weakness: CWE-667 (Improper Locking)

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

It affects 2 products.


Products: Heysoft Eventsave, Heysoft Eventsave\+.

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

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

## Is CVE-2002-1869 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1869 is a low-severity denial of service vulnerability in n/a, published on 28 Jun 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2002-1869 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-1869/ (Markdown: https://insights.sbomify.com/CVE-2002-1869/index.md)
```

## Sources

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

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