Mercury Audio Player multiple buffer overflow

map-multiple-bo (50288) The risk level is classified as HighHigh Risk


Mercury Audio Player is vulnerable to multiple buffer overflows, caused by improper bounds checking when parsing .m3u , .b4s, and .pls files. By persuading a victim to open a specially-crafted file, a remote attacker could overflow a buffer and execute arbitrary code on the system or cause the application to crash.


Base Score: 6.8
  Access Vector: Network
  Access Complexity: Medium
  Authentication: None
  Confidentiality Impact: Partial
  Integrity Impact: Partial
  Availability Impact: Partial
Temporal Score: 5.8
  Exploitability: Proof-of-Concept
  Remediation Level: Unavailable
  Report Confidence: Uncorroborated


Gain Access


No remedy available as of September 1, 2014.


  • Mercury Audio Player Web site: Mercury Audio Player - High Fidelity For The Future.
  • BID-34788: Mercury Audio Player 'm3u/b4s/pls' File Multiple Remote Stack Buffer Overflow Vulnerabilities
  • CVE-2009-4754: Stack-based buffer overflow in Mercury Audio Player 1.21 allows remote attackers to execute arbitrary code via a long string in a malformed playlist (.m3u) file.
  • CVE-2009-4755: Multiple stack-based buffer overflows in Mercury Audio Player 1.21 allow remote attackers to execute arbitrary code via a long string in a malformed (1) .b4s or (2) .pls playlist file.
  • OSVDB ID: 54170: Mercury Audio Player B4S Playlist File Handling Overflow
  • OSVDB ID: 63343: Mercury Audio Player M3U File Handling Overflow
  • SA34957: Mercury Audio Player Playlist Processing Buffer Overflows

Platforms Affected:

  • Mercury Audio Mercury Audio Player 1.21.04


Apr 30, 2009

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 ignore thisxforceignore this@ignore thisus.ignore thisibm.comignore this

Return to the main page