Vulnerability Note VU#158003

Power2Go buffer overflow vulnerability

Original Release date: 09 Dec 2011 | Last revised: 09 Dec 2011

Overview

Power2Go 8 contains a buffer overflow in the handling of project (.p2g) files, which can allow a remote, unauthenticated attacker to execute arbitrary code on a vulnerable system.

Description

According to CyberLink's website, "Power2Go 8 features all the tools you need to easily copy all your media to any disc. Now you can mount disc images as virtual drives, rip, copy and edit your music and experience the ultimate in convenience with drag and drop burning." Power2Go 8, and possibly prior versions, fails to perform adequate boundary checks on user-supplied input when parsing malformed project (.p2g) files causing a stack-based buffer overflow leading to possible remote code execution.

The reporter has also stated that the WaveEditor component of Power2Go 8 contains the same vulnerability when parsing WaveEditor project files (.wve).

Impact

By causing the Power2Go 8 application to parse a specially-crafted project (.p2g) file, a remote, unauthenticated attacker may be able to execute arbitrary code with the privileges of the user using the application.

Solution

We are currently unaware of a practical solution to this problem.


Use the Microsoft Enhanced Mitigation Experience Toolkit

The Microsoft Enhanced Mitigation Experience Toolkit (EMET) can be used to help prevent exploitation of these vulnerabilities.

Enable DEP in Microsoft Windows

Consider enabling Data Execution Prevention (DEP) in supported versions of Windows. DEP should not be treated as a complete workaround, but it can mitigate the execution of attacker-supplied code in some cases. Microsoft has published detailed technical information about DEP in Security Research & Defense blog posts "Understanding DEP as a mitigation technology" part 1 and part 2. DEP should be used in conjunction with the application of patches or other mitigations described in this document.

Note that when relying on DEP for exploit mitigation, it is important to use a system that supports Address Space Layout Randomization (ASLR) as well. ASLR is not supported by Windows XP or Windows Server 2003 or earlier. ASLR was introduced with Microsoft Windows Vista and Windows Server 2008. Please see the Microsoft SRD blog entry: On the effectiveness of DEP and ASLR for more details.

Vendor Information (Learn More)

VendorStatusDate NotifiedDate Updated
CyberLink CorporationAffected26 Oct 201130 Nov 2011
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A

References

Credit

Thanks to Tom Gregory of Spentera for reporting this vulnerability.

This document was written by Michael Orlando.

Other Information

  • CVE IDs: Unknown
  • Date Public: 09 Dec 2011
  • Date First Published: 09 Dec 2011
  • Date Last Updated: 09 Dec 2011
  • Severity Metric: 0.01
  • Document Revision: 6

Feedback

If you have feedback, comments, or additional information about this vulnerability, please send us email.