CVE-2005-2029
First published: Fri Jun 17 2005(Updated: )
amaroK Web Frontend 1.3 stores the globals.inc file under the web root without a .php extension and insufficient access control, which allows remote attackers to obtain the database username and password via a direct request to the file.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Amarok | =1.3 |
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-2005-2029?
CVE-2005-2029 is considered a medium severity vulnerability due to potential unauthorized access to sensitive information.
How do I fix CVE-2005-2029?
To fix CVE-2005-2029, ensure that the globals.inc file is not stored in the web root or rename it with a proper extension and restrict access appropriately.
What information can be leaked due to CVE-2005-2029?
CVE-2005-2029 allows remote attackers to access the database username and password stored in the globals.inc file.
Which version of amaroK Web Frontend is affected by CVE-2005-2029?
CVE-2005-2029 affects amaroK Web Frontend version 1.3.
What kind of attacks can be performed using the CVE-2005-2029 vulnerability?
Using CVE-2005-2029, an attacker can directly access sensitive database credentials by requesting the vulnerable globals.inc file.
- agent/references
- agent/type
- agent/first-publish-date
- agent/remedy
- agent/author
- agent/severity
- agent/weakness
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-historical
- agent/software-canonical-lookup-request
- collector/nvd-index
- agent/softwarecombine
- vendor/amarok
- canonical/amarok
- version/amarok/1.3