CVE-2008-2003: BadBlue 2.72 Personal Edition stores multiple programs in the web document root with insufficient access contr

This month

HIGH 7.5DOWNGRADE

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

BadBlue 2.72 Personal Edition stores multiple programs in the web document root with insufficient access control, which allows remote attackers to (1) cause a denial of service via multiple invocations of uninst.exe, and have an unknown impact via (2) badblue.exe and (3) dyndns.exe. NOTE: this can be leveraged for arbitrary remote code execution in conjunction with CVE-2007-6378.

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	2.8% (top 13%)
CISA exploited list	No
Weakness	CWE-264
Published	2008-04-28
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: badblue

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

Am I affected?

Timeline

2008-04-28 20:05 UTCPublished CVE record published
2026-06-16 22:52 UTCUpdated Record last modified

badblue badblue DOWNGRADE

Affected: 2.72

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.72

1. Check installed version

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

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

apt-cache madison badblue sudo apt install badblue=<VERSION_BEFORE_2.72> sudo apt-mark hold badblue

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

dnf --showduplicates list badblue sudo dnf downgrade badblue-<VERSION_BEFORE_2.72> sudo dnf versionlock add badblue

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-2008-2003?

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

Is CVE-2008-2003 being exploited?

CVE-2008-2003 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-2008-2003 affect?

CVE-2008-2003 affects badblue. Severity is high (CVSS 7.5). BadBlue 2.72 Personal Edition stores multiple programs in the web document root with insufficient access control, which allows remote attackers to (1) cause a denial of service via multiple invocations of uninst.exe, and have an unknown imp

How urgent is CVE-2008-2003?

Priority 48/100. High severity

Related CVEs

CVE-2007-6379 MEDIUM 5.0 UPGRADE BadBlue 2.72b and earlier allows remote attackers to obtain sensitive information via an invalid browse parame
CVE-2007-6378 HIGH 7.5 UPGRADE Directory traversal vulnerability in upload.dll in BadBlue 2.72b and earlier allows remote attackers to create
CVE-2007-6377 HIGH 7.5 UPGRADE Stack-based buffer overflow in the PassThru functionality in ext.dll in BadBlue 2.72b and earlier allows remot
CVE-2005-0595 HIGH 7.5 DOWNGRADE Buffer overflow in ext.dll in BadBlue 2.55 allows remote attackers to execute arbitrary code via a long mfcisa
CVE-2004-2374 MEDIUM 5.0 DOWNGRADE BadBlue 2.4 allows remote attackers to obtain the location of the server installation path via a request for p

References

← Back to latest CVEs