CVE-2005-3580: QDBM before 1.8.33-r2 allows local users in the portage group to increase privileges via a shared object in th

Routine

HIGH 7.2DOWNGRADE

CVE-2005-3580 is a high-severity flaw (CVSS 7.2) affecting qdbm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

QDBM before 1.8.33-r2 allows local users in the portage group to increase privileges via a shared object in the Portage temporary build directory, which is added to the search path allowing objects in it to be loaded at runtime.

Why this priority

High severity

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

Risk facts

CVSS score	7.2 (High)
EPSS exploit chance	0.4% (top 66%)
CISA exploited list	No
Published	2005-11-16
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: qdbm

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

Am I affected?

Timeline

2005-11-16 07:42 UTCPublished CVE record published
2026-06-16 22:17 UTCUpdated Record last modified

qdbm qdbm DOWNGRADE

Affected: 1.8.13 · 1.8.14 · 1.8.15 · 1.8.16 · 1.8.17 · 1.8.21 · 1.8.24 · 1.8.30

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.8.13

1. Check installed version

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

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

apt-cache madison qdbm sudo apt install qdbm=<VERSION_BEFORE_1.8.13> sudo apt-mark hold qdbm

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

dnf --showduplicates list qdbm sudo dnf downgrade qdbm-<VERSION_BEFORE_1.8.13> sudo dnf versionlock add qdbm

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

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

Is CVE-2005-3580 being exploited?

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

CVE-2005-3580 affects qdbm. Severity is high (CVSS 7.2). QDBM before 1.8.33-r2 allows local users in the portage group to increase privileges via a shared object in the Portage temporary build directory, which is added to the search path allowing objects in it to be loaded at runtime.

How urgent is CVE-2005-3580?

Priority 34/100. High severity

References

← Back to latest CVEs