ID CVE-2010-3653
Summary The Director module (dirapi.dll) in Adobe Shockwave Player before 11.5.9.615 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a Director movie with a crafted rcsL chunk containing a field whose value is used as a pointer offset, as exploited in the wild in October 2010. NOTE: some of these details are obtained from third party information.
References
Vulnerable Configurations
  • Adobe Shockwave Player 11.5.8.612
    cpe:2.3:a:adobe:shockwave_player:11.5.8.612
  • Adobe Shockwave Player 11.5.6.606
    cpe:2.3:a:adobe:shockwave_player:11.5.6.606
  • Adobe Shockwave Player 11.5.2.602
    cpe:2.3:a:adobe:shockwave_player:11.5.2.602
  • Adobe Shockwave Player 11.5.1.601
    cpe:2.3:a:adobe:shockwave_player:11.5.1.601
  • Adobe Shockwave Player 11.5.0.595
    cpe:2.3:a:adobe:shockwave_player:11.5.0.595
  • Adobe Shockwave Player 11.5.0.596
    cpe:2.3:a:adobe:shockwave_player:11.5.0.596
  • Adobe Shockwave Player 11.5.7.609
    cpe:2.3:a:adobe:shockwave_player:11.5.7.609
  • Adobe Shockwave Player 11.0.0.456
    cpe:2.3:a:adobe:shockwave_player:11.0.0.456
  • Adobe Macromedia Shockwave Player 11.0.3.471
    cpe:2.3:a:adobe:shockwave_player:11.0.3.471
  • Adobe Shockwave Player 10.2.0.023
    cpe:2.3:a:adobe:shockwave_player:10.2.0.023
  • Adobe Shockwave Player 10.2.0.022
    cpe:2.3:a:adobe:shockwave_player:10.2.0.022
  • Adobe Shockwave Player 10.1.0.11
    cpe:2.3:a:adobe:shockwave_player:10.1.0.11
  • Adobe Shockwave Player 10.2.0.021
    cpe:2.3:a:adobe:shockwave_player:10.2.0.021
  • Adobe Shockwave Player 10.1.4.020
    cpe:2.3:a:adobe:shockwave_player:10.1.4.020
  • Adobe Shockwave Player 10.1.1.016
    cpe:2.3:a:adobe:shockwave_player:10.1.1.016
  • Adobe Shockwave Player 10.1.0.011
    cpe:2.3:a:adobe:shockwave_player:10.1.0.011
  • Adobe Shockwave Player 10.0.1.004
    cpe:2.3:a:adobe:shockwave_player:10.0.1.004
  • Adobe Shockwave Player 10.0.0.210
    cpe:2.3:a:adobe:shockwave_player:10.0.0.210
  • Adobe Shockwave Player 9.0.383
    cpe:2.3:a:adobe:shockwave_player:9.0.383
  • Adobe Shockwave Player 9.0.432
    cpe:2.3:a:adobe:shockwave_player:9.0.432
  • Adobe Shockwave Player 8.5.321
    cpe:2.3:a:adobe:shockwave_player:8.5.321
  • Adobe Shockwave Player 8.5.324
    cpe:2.3:a:adobe:shockwave_player:8.5.324
  • Adobe Shockwave Player 8.0.204
    cpe:2.3:a:adobe:shockwave_player:8.0.204
  • Adobe Shockwave Player 8.0.205
    cpe:2.3:a:adobe:shockwave_player:8.0.205
  • Adobe Shockwave Player 8.5.1.100
    cpe:2.3:a:adobe:shockwave_player:8.5.1.100
  • Adobe Shockwave Player 8.5.323
    cpe:2.3:a:adobe:shockwave_player:8.5.323
  • Adobe Shockwave Player 8.5.325
    cpe:2.3:a:adobe:shockwave_player:8.5.325
  • Adobe Shockwave Player 8.0.196
    cpe:2.3:a:adobe:shockwave_player:8.0.196
  • Adobe Shockwave Player 8.0.196a
    cpe:2.3:a:adobe:shockwave_player:8.0.196a
  • Adobe Shockwave Player 8.5.1
    cpe:2.3:a:adobe:shockwave_player:8.5.1
  • Adobe Shockwave Player 8.5.1.106
    cpe:2.3:a:adobe:shockwave_player:8.5.1.106
  • Adobe Shockwave Player 8.0
    cpe:2.3:a:adobe:shockwave_player:8.0
  • Adobe Shockwave Player 8.5.1.105
    cpe:2.3:a:adobe:shockwave_player:8.5.1.105
  • Adobe Shockwave Player 8.5.1.103
    cpe:2.3:a:adobe:shockwave_player:8.5.1.103
  • Adobe Shockwave Player 6.0
    cpe:2.3:a:adobe:shockwave_player:6.0
  • Adobe Shockwave Player 5.0
    cpe:2.3:a:adobe:shockwave_player:5.0
  • Adobe Shockwave Player 4.0
    cpe:2.3:a:adobe:shockwave_player:4.0
  • Adobe Shockwave Player 3.0
    cpe:2.3:a:adobe:shockwave_player:3.0
  • Adobe Shockwave Player 2.0
    cpe:2.3:a:adobe:shockwave_player:2.0
  • cpe:2.3:a:adobe:shockwave_player:1.0
CVSS
Base: 9.3 (as of 27-10-2010 - 09:17)
Impact:
Exploitability:
CWE CWE-119
CAPEC
  • Buffer Overflow via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Overflow Buffers
    Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an attacker. As a consequence, an attacker is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the attackers' choice.
  • Client-side Injection-induced Buffer Overflow
    This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service.
  • Filter Failure through Buffer Overflow
    In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered).
  • MIME Conversion
    An attacker exploits a weakness in the MIME conversion routine to cause a buffer overflow and gain control over the mail server machine. The MIME system is designed to allow various different information formats to be interpreted and sent via e-mail. Attack points exist when data are converted to MIME compatible format and back.
  • Overflow Binary Resource File
    An attack of this type exploits a buffer overflow vulnerability in the handling of binary resources. Binary resources may include music files like MP3, image files like JPEG files, and any other binary file. These attacks may pass unnoticed to the client machine through normal usage of files, such as a browser loading a seemingly innocent JPEG file. This can allow the attacker access to the execution stack and execute arbitrary code in the target process. This attack pattern is a variant of standard buffer overflow attacks using an unexpected vector (binary files) to wrap its attack and open up a new attack vector. The attacker is required to either directly serve the binary content to the victim, or place it in a locale like a MP3 sharing application, for the victim to download. The attacker then is notified upon the download or otherwise locates the vulnerability opened up by the buffer overflow.
  • Buffer Overflow via Symbolic Links
    This type of attack leverages the use of symbolic links to cause buffer overflows. An attacker can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking.
  • Overflow Variables and Tags
    This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The attacker crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.
  • Buffer Overflow via Parameter Expansion
    In this attack, the target software is given input that the attacker knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.
  • Buffer Overflow in an API Call
    This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An attacker who has access to an API may try to embed malicious code in the API function call and exploit a buffer overflow vulnerability in the function's implementation. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.
  • Buffer Overflow in Local Command-Line Utilities
    This attack targets command-line utilities available in a number of shells. An attacker can leverage a vulnerability found in a command-line utility to escalate privilege to root.
Access
VectorComplexityAuthentication
NETWORK MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
COMPLETE COMPLETE COMPLETE
exploit-db via4
  • description Adobe Shockwave rcsL Memory Corruption. CVE-2010-3653. Remote exploit for windows platform
    id EDB-ID:16594
    last seen 2016-02-02
    modified 2010-10-22
    published 2010-10-22
    reporter metasploit
    source https://www.exploit-db.com/download/16594/
    title Adobe Shockwave - rcsL Memory Corruption
  • description Adobe Shockwave player rcsL chunk memory corruption 0day. CVE-2010-3653. Remote exploit for windows platform
    file exploits/windows/remote/15296.txt
    id EDB-ID:15296
    last seen 2016-02-01
    modified 2010-10-21
    platform windows
    port
    published 2010-10-21
    reporter Abysssec
    source https://www.exploit-db.com/download/15296/
    title Adobe Shockwave Player - rcsL chunk memory corruption 0day
    type remote
metasploit via4
description This module exploits a weakness in the Adobe Shockwave player's handling of Director movies (.DIR). A memory corruption vulnerability occurs through an undocumented rcsL chunk.
id MSF:EXPLOIT/WINDOWS/BROWSER/ADOBE_SHOCKWAVE_RCSL_CORRUPTION
last seen 2019-03-13
modified 2017-07-24
published 2010-10-22
reliability Normal
reporter Rapid7
source https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/windows/browser/adobe_shockwave_rcsl_corruption.rb
title Adobe Shockwave rcsL Memory Corruption
nessus via4
  • NASL family MacOS X Local Security Checks
    NASL id MACOSX_SHOCKWAVE_PLAYER_APSB10-25.NASL
    description The remote Mac OS X host contains a version of Adobe Shockwave Player that is 11.5.8.612 or earlier. It is, therefore, affected by multiple vulnerabilities : - A memory corruption issue exists that allows code execution. Note that there are reports that this issue is being exploited in the wild. (CVE-2010-3653) - A heap-based buffer overflow vulnerability allows code execution. (CVE-2010-2582) - Multiple memory corruption issues in the 'dirapi.dll' module allow code execution. (CVE-2010-2581, CVE-2010-3655, CVE-2010-4084, CVE-2010-4085, CVE-2010-4086, CVE-2010-4088) - Multiple memory corruption issues in the 'IML32.dll' module allow code execution. (CVE-2010-4087, CVE-2010-4089) - A memory corruption issue allows code execution. (CVE-2010-4090)
    last seen 2019-02-21
    modified 2018-07-14
    plugin id 80174
    published 2014-12-22
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=80174
    title Adobe Shockwave Player <= 11.5.8.612 (APSB10-25) (Mac OS X)
  • NASL family Windows
    NASL id SHOCKWAVE_PLAYER_APSB10-25.NASL
    description The remote Windows host contains a version of Adobe's Shockwave Player that is earlier than 11.5.9.615. Such versions are potentially affected by the following issues : - A memory corruption issue exists that could lead to code execution. Note that there are reports this issue is being exploited in the wild. (CVE-2010-3653) - A heap-based buffer overflow vulnerability could lead to code execution. (CVE-2010-2582) - Multiple memory corruption issues in the 'dirapi.dll' module could lead to code execution. (CVE-2010-2581, CVE-2010-3655, CVE-2010-4084, CVE-2010-4085, CVE-2010-4086, CVE-2010-4088) - Multiple memory corruption issues in the 'IML32.dll' module could lead to code execution. (CVE-2010-4087, CVE-2010-4089) - A memory corruption issue that could lead to code execution. (CVE-2010-4090)
    last seen 2019-02-21
    modified 2018-07-27
    plugin id 50387
    published 2010-10-28
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=50387
    title Shockwave Player < 11.5.9.615
oval via4
accepted 2014-11-10T04:00:10.458-05:00
class vulnerability
contributors
  • name SecPod Team
    organization SecPod Technologies
  • name Shane Shaffer
    organization G2, Inc.
  • name Maria Mikhno
    organization ALTX-SOFT
definition_extensions
comment Adobe Shockwave Player is installed
oval oval:org.mitre.oval:def:5990
description The Director module (dirapi.dll) in Adobe Shockwave Player before 11.5.9.615 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a Director movie with a crafted rcsL chunk containing a field whose value is used as a pointer offset, as exploited in the wild in October 2010. NOTE: some of these details are obtained from third party information.
family windows
id oval:org.mitre.oval:def:11285
status accepted
submitted 2010-11-26T14:17:35
title Denial of service (memory corruption) via a Director movie with a crafted rcsL chunk in the Director module (dirapi.dll) in Adobe Shockwave Player before 11.5.9.615
version 69
packetstorm via4
data source https://packetstormsecurity.com/files/download/95121/adobe_shockwave_rcsl_corruption.rb.txt
id PACKETSTORM:95121
last seen 2016-12-05
published 2010-10-25
reporter David Kennedy
source https://packetstormsecurity.com/files/95121/Adobe-Shockwave-rcsL-Memory-Corruption.html
title Adobe Shockwave rcsL Memory Corruption
refmap via4
bid 44291
cert-vn VU#402231
confirm http://www.adobe.com/support/security/bulletins/apsb10-25.html
exploit-db 15296
misc http://www.abysssec.com/blog/2010/10/adobe-shockwave-player-rcsl-chunk-memory-corruption-0day/
sectrack 1024635
vupen ADV-2010-2752
xf adobe-shockwave-rcsl-code-exec(62688)
saint via4
bid 44291
description Adobe Shockwave Director rcsL Chunk Remote Code Execution
id misc_shockwave
osvdb 68803
title adobe_shockwave_director_rcsl_chunk
type client
Last major update 18-07-2011 - 00:00
Published 26-10-2010 - 14:00
Last modified 18-09-2017 - 21:31
Back to Top