CVE-2010-3440: babiloo 2.0.9 before 2.0.11 creates temporary files with predictable names when downloading and unpacking dict

Routine

MEDIUM 5.5WATCHLISTUPGRADEMITIGATE

CVE-2010-3440 is a medium-severity flaw (CVSS 5.5) affecting babiloo, debian linux. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

babiloo 2.0.9 before 2.0.11 creates temporary files with predictable names when downloading and unpacking dictionary files, allowing a local attacker to overwrite arbitrary files.

Why this priority

On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 83%)
CISA exploited list	No
Weakness	CWE-494
Published	2019-11-12
Last modified	2026-06-16

Publisher (CNA): Red Hat, Inc. · Vendor: babiloo project · debian

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

Am I affected?

Timeline

2019-11-12 22:15 UTCPublished CVE record published
2026-06-16 23:22 UTCUpdated Record last modified

babiloo project babiloo UPGRADE

Affected: >= 2.0.9 and < 2.0.11

Fixed in: 2.0.11

Safe to downgrade to: a release before 2.0.9

1. Check installed version

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

2. UPGRADE to 2.0.11 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade babiloo

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade babiloo

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.0.9 (Debian / Ubuntu)

apt-cache madison babiloo sudo apt install babiloo=<VERSION_BEFORE_2.0.9> sudo apt-mark hold babiloo

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list babiloo sudo dnf downgrade babiloo-<VERSION_BEFORE_2.0.9> sudo dnf versionlock add babiloo

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.

debian debian linux MITIGATE

Affected: 8.0 · 9.0 · 10.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 8.0

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

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-2010-3440?

babiloo: upgrade to 2.0.11; debian linux: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2010-3440 being exploited?

CVE-2010-3440 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-2010-3440 affect?

CVE-2010-3440 affects babiloo, debian linux. Severity is medium (CVSS 5.5). babiloo 2.0.9 before 2.0.11 creates temporary files with predictable names when downloading and unpacking dictionary files, allowing a local attacker to overwrite arbitrary files.

How urgent is CVE-2010-3440?

Priority 29/100. On your watchlist

Software pages

Debian vulnerabilities

References

← Back to latest CVEs