CVE-2007-6379
First published: Sat Dec 15 2007(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Badblue | <=2.72b |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2007-6379?
CVE-2007-6379 has a medium severity level due to its potential to expose sensitive information.
How do I fix CVE-2007-6379?
To fix CVE-2007-6379, upgrade to BadBlue version 2.72c or later.
What type of information can be exposed due to CVE-2007-6379?
CVE-2007-6379 can expose the installation path of the BadBlue server in error messages.
Which versions of BadBlue are affected by CVE-2007-6379?
CVE-2007-6379 affects BadBlue versions 2.72b and earlier.
Can CVE-2007-6379 lead to further attacks?
Yes, CVE-2007-6379 may assist attackers in targeting the system more effectively by exposing its installation path.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/references
- agent/severity
- agent/weakness
- agent/last-modified-date
- agent/description
- agent/first-publish-date
- agent/softwarecombine
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/badblue
- canonical/badblue
- version/badblue/2.72b