CVE-2005-1917: kpopper 1.0 and earlier allows local users to create and overwrite arbitrary files via a symlink attack on the

Routine

LOW 2.1DOWNGRADE

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

kpopper 1.0 and earlier allows local users to create and overwrite arbitrary files via a symlink attack on the .popper-new temporary file.

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 78%)
CISA exploited list	No
Published	2005-07-05
Last modified	2026-06-16

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

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

Am I affected?

Timeline

2005-07-05 04:00 UTCPublished CVE record published
2026-06-16 22:13 UTCUpdated Record last modified

kpopper kpopper DOWNGRADE

Affected: 1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

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

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

apt-cache madison kpopper sudo apt install kpopper=<VERSION_BEFORE_1.0> sudo apt-mark hold kpopper

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

dnf --showduplicates list kpopper sudo dnf downgrade kpopper-<VERSION_BEFORE_1.0> sudo dnf versionlock add kpopper

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-1917?

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

Is CVE-2005-1917 being exploited?

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

CVE-2005-1917 affects kpopper. Severity is low (CVSS 2.1). kpopper 1.0 and earlier allows local users to create and overwrite arbitrary files via a symlink attack on the .popper-new temporary file.

How urgent is CVE-2005-1917?

Priority 13/100. No elevated risk signals yet.

References

← Back to latest CVEs