CVE-2005-1055: TowerBlog 0.6 and earlier stores the login data file under the web root, which allows remote attackers to obta

This month

HIGH 7.5DOWNGRADE

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

TowerBlog 0.6 and earlier stores the login data file under the web root, which allows remote attackers to obtain the MD5 checksums of the username and password via a direct request to the _dat/login file.

Why this priority

High severity

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

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	1.6% (top 24%)
CISA exploited list	No
Published	2005-04-10
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: towerblog

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

Am I affected?

Timeline

2005-04-10 04:00 UTCPublished CVE record published
2026-06-16 22:12 UTCUpdated Record last modified

towerblog towerblog DOWNGRADE

Affected: 0.2 · 0.4_r1 · 0.6 · 0.6_r1

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.2

1. Check installed version

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

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

apt-cache madison towerblog sudo apt install towerblog=<VERSION_BEFORE_0.2> sudo apt-mark hold towerblog

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

dnf --showduplicates list towerblog sudo dnf downgrade towerblog-<VERSION_BEFORE_0.2> sudo dnf versionlock add towerblog

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

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

Is CVE-2005-1055 being exploited?

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

CVE-2005-1055 affects towerblog. Severity is high (CVSS 7.5). TowerBlog 0.6 and earlier stores the login data file under the web root, which allows remote attackers to obtain the MD5 checksums of the username and password via a direct request to the _dat/login file.

How urgent is CVE-2005-1055?

Priority 45/100. High severity

References

← Back to latest CVEs