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 wr

Routine

LOW 3.3DOWNGRADEDOWNGRADE

CVE-2002-1869 is a low-severity flaw (CVSS 3.3) affecting eventsave, eventsave\+. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	3.3 (Low)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 76%)
CISA exploited list	No
Weakness	CWE-667
Published	2002-12-31
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: heysoft

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2002-12-31 05:00 UTCPublished CVE record published
2026-06-16 22:00 UTCUpdated Record last modified

heysoft eventsave DOWNGRADE

Affected: 5.1 · 5.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 5.1

1. Check installed version

apt-cache policy eventsave || rpm -q eventsave || eventsave --version

2. No fixed release: DOWNGRADE to a release before 5.1 (Debian / Ubuntu)

apt-cache madison eventsave sudo apt install eventsave=<VERSION_BEFORE_5.1> sudo apt-mark hold eventsave

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list eventsave sudo dnf downgrade eventsave-<VERSION_BEFORE_5.1> sudo dnf versionlock add eventsave

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

heysoft eventsave\+ DOWNGRADE

Affected: 5.1 · 5.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 5.1

1. Check installed version

apt-cache policy eventsave+ || rpm -q eventsave+ || eventsave+ --version

2. No fixed release: DOWNGRADE to a release before 5.1 (Debian / Ubuntu)

apt-cache madison eventsave+ sudo apt install eventsave+=<VERSION_BEFORE_5.1> sudo apt-mark hold eventsave+

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list eventsave+ sudo dnf downgrade eventsave+-<VERSION_BEFORE_5.1> sudo dnf versionlock add eventsave+

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2002-1869?

eventsave: downgrade or apply the listed mitigation; eventsave\+: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2002-1869 being exploited?

CVE-2002-1869 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2002-1869 affect?

CVE-2002-1869 affects eventsave, eventsave\+. Severity is low (CVSS 3.3). 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 Micros

How urgent is CVE-2002-1869?

Priority 18/100. No elevated risk signals yet.

References

← Back to latest CVEs