How severe is CVE-2007-6379?

CVE-2007-6379 has a CVSS 2.0 base score of 5.0, rated medium severity.

Is CVE-2007-6379 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (87th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2007-6379?

CVE-2007-6379 affects Badblue. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2007-6379?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2007-6379 published?

CVE-2007-6379 was published on 2007-12-15 and last updated on 2026-06-16.

CVE-2007-6379

CVE-2007-6379 is a medium-severity vulnerability in Badblue with a CVSS 2.0 base score of 5.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-16.

Key facts

Severity: Medium (CVSS 2.0 base score 5.0)
EPSS exploit prediction: 3% (87th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-16
Affected product: Badblue
Published: 2007-12-15
Last modified: 2026-06-16

Description

BadBlue 2.72b and earlier allows remote attackers to obtain sensitive information via an invalid browse parameter, which reveals the installation path in an error message.

Frequently asked questions

What is CVE-2007-6379?: BadBlue 2.72b and earlier allows remote attackers to obtain sensitive information via an invalid browse parameter, which reveals the installation path in an error message.
How severe is CVE-2007-6379?: CVE-2007-6379 has a CVSS 2.0 base score of 5.0, rated medium severity.
Is CVE-2007-6379 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (87th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2007-6379?: CVE-2007-6379 affects Badblue. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2007-6379?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2007-6379 published?: CVE-2007-6379 was published on 2007-12-15 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:badblue:badblue:*:*:*:*:*:*:*:*

More vulnerabilities in Badblue

CVE-2008-2003 — High (CVSS 7.5): BadBlue 2.72 Personal Edition stores multiple programs in the web document root with insufficient access control, which…
CVE-2007-6378 — High (CVSS 7.5): Directory traversal vulnerability in upload.dll in BadBlue 2.72b and earlier allows remote attackers to create or…
CVE-2007-6377 — High (CVSS 7.5): Stack-based buffer overflow in the PassThru functionality in ext.dll in BadBlue 2.72b and earlier allows remote…

All CVEs affecting Badblue →

Other CWE-16 vulnerabilities

CVE-2013-4316 — Critical (CVSS 10.0): Apache Struts 2.0.0 through 2.3.15.1 enables Dynamic Method Invocation by default, which has unknown impact and attack…
CVE-2013-1221 — Critical (CVSS 10.0): The Tomcat Web Management feature in Cisco Unified Customer Voice Portal (CVP) Software before 9.0.1 ES 11 does not…
CVE-2011-4501 — Critical (CVSS 10.0): The UPnP IGD implementation in Edimax EdiLinux on the Edimax BR-6104K with firmware before 3.25, Edimax 6114Wg,…
CVE-2010-4586 — Critical (CVSS 10.0): The default configuration of Opera before 11.00 enables WebSockets functionality, which has unspecified impact and…
CVE-2010-2977 — Critical (CVSS 10.0): Cisco Unified Wireless Network (UWN) Solution 7.x before 7.0.98.0 does not properly implement TLS and SSL, which has…
CVE-2010-2276 — Critical (CVSS 10.0): The default configuration of the build process in Dojo 0.4.x before 0.4.4, 1.0.x before 1.0.3, 1.1.x before 1.1.2,…

Browse all CWE-16 vulnerabilities →