628 matches found
CVE-2005-2754
CVE-2005-2754 refers to an integer overflow in Apple QuickTime before 7.0.3 that can enable remote code execution when a crafted MOV file with “Improper movie attributes” is loaded. The issue is documented across multiple sources as affecting QuickTime on Mac OS X and Windows, with the overflow p...
CVE-2005-2753: Undefined Security Weakness
Integer overflow in Apple QuickTime before 7.0.3 allows user-assisted attackers to execute arbitrary code via a crafted MOV file that causes a sign extension of the length element in a Pascal style string...
CVE-2005-2754: Undefined Security Weakness
Integer overflow in Apple QuickTime before 7.0.3 allows user-assisted attackers to execute arbitrary code via a crafted MOV file with "Improper movie attributes."...
[Full-disclosure] Advisory: Apple QuickTime Player Remote Integer Overflow (1)
Apple QuickTime Player Remote Integer Overflow 1 by Piotr Bania [email protected] http://pb.specialised.info All rights reserved. CVE-ID: CVE-2005-2753 Original location: http://pb.specialised.info/all/adv/quicktime-mov-io1-adv.txt Severity: Critical - remote code execution. Software affected...
Variable-length Fnstenv/mov Dword XOR Encoder
This encoder uses a variable-length mov equivalent instruction with fnstenv for getip. This module requires Metasploit: https://metasploit.com/download Current source: https://github.com/rapid7/metasploit-framework class MetasploitModule 'Variable-length Fnstenv/mov Dword XOR Encoder',...
CVE-2005-1579: Undefined Security Weakness
Apple QuickTime Player 7.0 on Mac OS X 10.4 allows remote attackers to obtain sensitive information via a .mov file with a Quartz Composer composition .qtz file that uses certain patches to read local information, then other patches to send the information to the attacker...
Quicktime < 7.0.1 Web Plugin Information Disclosure
Binary data 2899.prm...
CVE-2004-0431: Undefined Security Weakness
Integer overflow in Apple QuickTime QuickTime.qts before 6.5.1 allows attackers to execute arbitrary code via a large "number of entries" field in the sample-to-chunk table data for a .mov movie file, which leads to a heap-based buffer overflow...