CVE-2005-1915: The log4sh_readProperties function in log4sh 1.2.5 and earlier allows local users to overwrite arbitrary files

Routine

LOW 2.1DOWNGRADE

CVE-2005-1915 is a low-severity flaw (CVSS 2.1) affecting log4sh. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The log4sh_readProperties function in log4sh 1.2.5 and earlier allows local users to overwrite arbitrary files via a symlink attack on predictable log4sh.$$ filenames.

Why this priority

No elevated risk signals yet

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

Risk facts

CVSS score	2.1 (Low)
EPSS exploit chance	0.3% (top 72%)
CISA exploited list	No
Published	2005-09-02
Last modified	2026-06-16

Publisher (CNA): Red Hat, Inc. · Vendor: log4sh

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

Am I affected?

Timeline

2005-09-02 17:03 UTCPublished CVE record published
2026-06-16 22:13 UTCUpdated Record last modified

log4sh log4sh DOWNGRADE

Affected: 1.2.3 · 1.2.4 · 1.2.5

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.2.3

1. Check installed version

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

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

apt-cache madison log4sh sudo apt install log4sh=<VERSION_BEFORE_1.2.3> sudo apt-mark hold log4sh

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

dnf --showduplicates list log4sh sudo dnf downgrade log4sh-<VERSION_BEFORE_1.2.3> sudo dnf versionlock add log4sh

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-2005-1915?

log4sh: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-1915 being exploited?

CVE-2005-1915 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-2005-1915 affect?

CVE-2005-1915 affects log4sh. Severity is low (CVSS 2.1). The log4sh_readProperties function in log4sh 1.2.5 and earlier allows local users to overwrite arbitrary files via a symlink attack on predictable log4sh.$$ filenames.

How urgent is CVE-2005-1915?

Priority 14/100. No elevated risk signals yet.

References

← Back to latest CVEs