The vulnerable system is bound to a protocol stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared proximity (e.g., Bluetooth, NFC, or IEEE 802.11) or logical network (e.g., local IP subnet), or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN within an administrative network zone). One example of an Adjacent attack would be an ARP (IPv4) or neighbor discovery flood leading to a denial of service on the local LAN segment (e.g., CVE-2013-6014).
Attack Complexity
High
AC
The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques. The attacker must have additional methods available to bypass security measures in place. For example, circumvention of address space randomization (ASLR) or data execution prevention must be performed for the attack to be successful. Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Privileges Required
None
PR
The attacker is unauthenticated prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
Scope
Unchanged
S
An exploited vulnerability can only affect resources managed by the same security authority. In the case of a vulnerability in a virtualized environment, an exploited vulnerability in one guest instance would not affect neighboring guest instances.
Confidentiality
High
C
There is total information disclosure, resulting in all data on the system being revealed to the attacker, or there is a possibility of the attacker gaining control over confidential data.
Integrity
High
I
There is a total compromise of system integrity. There is a complete loss of system protection, resulting in the attacker being able to modify any file on the target system.
Availability
High
A
There is a total shutdown of the affected resource. The attacker can deny access to the system or data, potentially causing significant loss to the organization.
NSFOCUS Security Advisory (SA2006-01)
Winamp m3u File Processing Buffer Overflow Vulnerability
Release Date: 2006-02-23
CVE ID: CVE-2006-0720
http://www.nsfocus.com/english/homepage/research/0601.htm
Affected systems & software
===========================
Nullsoft Winamp 5.12
Nullsoft Winamp 5.13
Unaffected systems & software
=============================
Nullsoft Winamp 5.2
Summary
=========
Winamp is a popular media player that supports various media formats and
playlist formats, including m3u and pls formats.
NSFocus Security Team discovered a buffer overflow vulnerability when Winamp
processes .m3u files, which might cause Winamp to crash or even execute
arbitrary code when a user load a malicious .m3u file and play.
Description
============
Winamp can play files by loading .m3u file. When the playing is paused or stopped,
Winamp will reset the title of the program, where function strncpy() is incorrectly
called, resulting in a static buffer overflow.
An attacker can cause winamp to crash by crafting a malicious .m3u file.
Remote code execution is possible but difficult.
Workaround
=============
Cancel .m3u file association to Winamp, and do not open untrusted .m3u files.
Vendor Status
==============
2006.02.13 Informed the vendor.
2006.02.15 The vendor confirmed the vulnerability.
2006.02.21 The vendor releases a new version to fix the vulnerability.
The vendor has released Winamp 5.2 to fix this vulnerability, which is available
for download at:
http://www.winamp.com/player/
http://forums.winamp.com/showthread.php?threadid=238648
Additional Information
========================
The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CVE-2006-0720 to this issue. This is a candidate for inclusion in the
CVE list (http://cve.mitre.org), which standardizes names for security problems.
Candidates may change significantly before they become official CVE entries.
Acknowledgment
===============
Liu Yexin of NSFocus Security Team found the vulnerability.
DISCLAIMS
==========
THE INFORMATION PROVIDED IS RELEASED BY NSFOCUS "AS IS" WITHOUT WARRANTY
OF ANY KIND. NSFOCUS DISCLAIMS ALL WARRANTIES, EITHER EXPRESSED OR IMPLIED,
EXCEPT FOR THE WARRANTIES OF MERCHANTABILITY. IN NO EVENT SHALL NSFOCUS
BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT,
INCIDENTAL,CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,
EVEN IF NSFOCUS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
DISTRIBUTION OR REPRODUCTION OF THE INFORMATION IS PROVIDED THAT THE
ADVISORY IS NOT MODIFIED IN ANY WAY.
Copyright 1999-2006 NSFOCUS. All Rights Reserved. Terms of use.
NSFOCUS Security Team <security (at) nsfocus (dot) com [email concealed]>
NSFOCUS INFORMATION TECHNOLOGY CO.,LTD
(http://www.nsfocus.com)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQBD/Vgo1794d8am9toRAjjLAKCJyCZ4QBGQBVVtisBXkrJ7hmSJ6QCeJbhT
3PSlkDWxaJzBbabGF/wJ3nQ=
=8x9O
-----END PGP SIGNATURE-----
This information is provided for TESTING and LEGAL RESEARCH purposes only. All trademarks used are properties of their respective owners. By visiting this website you agree to Terms of Use and Privacy Policy and Impressum