Some vulnerabilities have been reported in Adobe Flash Player, which can be exploited by malicious people to conduct cross-site scripting attacks or compromise a user's system.

1) An error exists in the ActionScript Virtual Machine 2 (AVM2) when handling the "newfunction" instruction. This can be exploited to incorrectly calculate the location of a pointer later used to obtain an object reference, which may result in execution of user-controlled data in memory.

NOTE: This vulnerability is reportedly being actively exploited.

2) An unspecified error can be exploited to exhaust available memory and potentially execute arbitrary code.

3) An integer overflow error in the "newFrameState()" method can be exploited to cause a buffer overflow as the "max_scope" and "max_stack" variables are not properly validated.

4) An array indexing error can be exploited to potentially execute arbitrary code.

5) An error when calculating length values from STSC, STSZ, and STCO atoms in embedded MP4 files can be exploited to corrupt heap memory and potentially execute arbitrary code.

6) An unspecified error can be exploited to potentially execute arbitrary code.

7) A use-after-free error when processing an image placed on a linked list can be exploited to potentially execute arbitrary code.

8) An unspecified error can be exploited to corrupt memory and potentially execute arbitrary code.

9) Another unspecified error can be exploited to corrupt memory and potentially execute arbitrary code.

10) An error can be exploited to cause a heap-based buffer overflow and potentially execute arbitrary code.

11) An error related to the use of a pointer can be exploited to corrupt memory and potentially execute arbitrary code.

12) An integer overflow error can be exploited to corrupt memory and potentially execute arbitrary code.

13) An error in the implementation of the "DefineBits" tag when decompressing JPEG data can be exploited to corrupt heap memory and potentially execute arbitrary code.

14) An error related to an invalid pointer can be exploited to potentially execute arbitrary code.

15) Another error related to an invalid pointer can be exploited to potentially execute arbitrary code.

16) An unspecified error can be exploited to corrupt memory and potentially execute arbitrary code.

17) A second unspecified error can be exploited to corrupt memory and potentially execute arbitrary code.

18) A third unspecified error can be exploited to corrupt memory and potentially execute arbitrary code.

19) A fourth unspecified error can be exploited to corrupt memory and potentially execute arbitrary code.

20) An error when parsing URLs can be exploited to execute arbitrary script code in a different domain in Firefox and Chrome browsers.

21) An unspecified error can be exploited to corrupt memory and potentially execute arbitrary code.

22) An integer overflow error can be exploited to corrupt memory and potentially execute arbitrary code.

23) An unspecified error can be exploited to corrupt memory and potentially execute arbitrary code.

24) An integer overflow error can be exploited to corrupt memory and potentially execute arbitrary code.

25) An unspecified error can be exploited to corrupt memory and potentially execute arbitrary code.

26) An unspecified error can be exploited to cause a buffer overflow and potentially execute arbitrary code.

27) An unspecified error can be exploited to cause a crash or potentially execute arbitrary code.

28) An unspecified error can be exploited to corrupt memory and potentially execute arbitrary code.

29) An error in the connect method exposed via ActionScript native object number 2200 can be exploited to corrupt memory and potentially execute arbitrary code.

30) An error when running on VMWare systems with VMWare Tools enabled can be exploited to corrupt memory and potentially execute arbitrary code.

31) An operand passed to an undocumented opcode within AVM2 is used as an offset to a structure containing a function pointer, which can be exploited to reference user-controlled data by passing an invalid operand.

Solution
Update to version 9.0.277.0 or 10.1.53.64.
Further details available in Customer Area

Provided and/or discovered by
1) Reported as a 0-day. Independently discovered by Will Dormann, CERT/CC.
3) An anonymous person via ZDI.
4, 7) An anonymous person via iDefense
5, 29) Damian Put via ZDI
13) An anonymous person and Tielei Wang (ICST-ERCIS), reported via ZDI
31) Dionysus Blazakis via ZDI.

The vendor also credits:
1) Lockheed Martin CIRT, Members of the Defense Security Information Exchange (DSIE)
2) Ralph Loader, Innaworks Development Limited.
6) Bing Liu of Fortinet's FortiGuard Labs, Tavis Ormandy, and Will Dormann of CERT/CC.
8) Megumi Yanagishita, Palo Alto Networks Inc.
9) Bing Liu of Fortinet's FortiGuard Labs
10, 14, 15) Nicolas Joly, Vupen.
11) Manuel Caballero and Microsoft Vulnerability Research (MSVR)
12) Tielei Wang, ICST-ERCIS.
16-19) Bo Qu, Palo Alto Networks.
20) Ezio Anselmo Mazarim Fernandes
21-28) Tavis Ormandy, Google Security Team.
30) Haifei Li of Fortinet's FortiGuard Labs

Changelog
Further details available in Customer Area

Original Advisory
Adobe:
http://www.adobe.com/support/security/bulletins/apsb10-14.html
http://www.adobe.com/support/security/advisories/apsa10-01.html

US-CERT VU#486225:
http://www.kb.cert.org/vuls/id/486225

iDefense:
http://labs.idefense.com/intelligence/vulnerabilities/display.php?id=871
http://labs.idefense.com/intelligence/vulnerabilities/display.php?id=872

ZDI:
http://www.zerodayinitiative.com/advisories/ZDI-10-109/
http://www.zerodayinitiative.com/advisories/ZDI-10-110/
http://www.zerodayinitiative.com/advisories/ZDI-10-111/
http://www.zerodayinitiative.com/advisories/ZDI-10-114/
http://www.zerodayinitiative.com/advisories/ZDI-10-115/

Other references
Further details available in Customer Area

Deep Links
Links available in Customer Area