Wimpy MP3 Player wimpy_trackplays.php no authentication
| wimpy-wimpytrackplays-no-auth (24770) |  Medium Risk |
Description:
Wimpy MP3 Player could allow a remote attacker to modify the trackme.txt file due to no authentication restrictions on the wimpy_trackplays.php script. An attacker could use this vulnerability to write to the trackme.txt file, which could lead to other attacks against the affected system.
*CVSS:
| Base Score: | 3.5 |
| Access Vector: | Remote |
| Access Complexity: | Low |
| Authentication: | Not Required |
| Confidentiality Impact: | None |
| Integrity Impact: | Partial |
| Availability Impact: | None |
| Temporal Score: | 2.8 |
| Exploitability: | Unproven |
| Remediation Level: | Unavailable |
| Report Confidence: | Uncorroborated |
Consequences:
Bypass Security
Remedy:
No remedy available as of July 9, 2011.
References:
- Full-Disclosure Mailing List, Wed Feb 15 2006 - 19:55:15 CST : Wimpy MP3 Player - Text file overwrite vulnerability.
- Wimpy MP3 Player Web site: Wimpy: Streaming WebSite Audio & Video Tools.
- BID-16696: Wimpy MP3 Player Text File Overwrite Weakness
- CVE-2006-0787: wimpy_trackplays.php in Plaino Wimpy MP3 Player, possibly 5.2 and earlier, allows remote attackers to insert arbitrary strings into trackme.txt via the (1) trackFile, (2) trackArtist, and (3) trackTitle parameters, which can result in providing false information about songs, occupying excessive disk space with very long parameter values, and storing executable code that might be invoked through a different vulnerability. NOTE: since this issue, as described by the original researcher, is entirely dependent on the presence of another vulnerability, it could be argued that Wimpy cannot be responsible for how its data file is processed by applications outside of its control. Since this issue might only be useful as a facilitator manipulation in another vulnerability, perhaps it should not be
- SA18900: Wimpy MP3 Player trackme.txt File Modification Weakness
Platforms Affected:
- wimpy Wimpy MP3 Player
Reported:
Feb 15, 2006
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net
* According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall IBM be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.