CVE-2008-2320

CVE-2008-2320 is a stack-based buffer overflow in CarbonCore used by Apple Mac OS X (10.4.11 and 10.5.4), iPhone OS 1.0–2.2.1, and iPod touch OS 1.1–2.2.1. The flaw allows context-dependent attackers to execute arbitrary code or cause an application crash by providing a long filename to the file ...

CVE-2008-2320

Stack-based buffer overflow in CarbonCore in Apple Mac OS X 10.4.11 and 10.5.4, iPhone OS 1.0 through 2.2.1, and iPhone OS for iPod touch 1.1 through 2.2.1 allows context-dependent attackers to execute arbitrary code or cause a denial of service application crash via a long filename to the file...

CVE-2008-2320: Improper Restriction of Operations within the Bounds of a Memory Buffer

Stack-based buffer overflow in CarbonCore in Apple Mac OS X 10.4.11 and 10.5.4, iPhone OS 1.0 through 2.2.1, and iPhone OS for iPod touch 1.1 through 2.2.1 allows context-dependent attackers to execute arbitrary code or cause a denial of service application crash via a long filename to the file...

Safari installed in iPod touch and iPhone vulnerable in handling server certificates

Overview Safari web browser installed in iPod touch and iPhone contains a vulnerability which allows a self-signed or invalid server certificate to be accepted without the user's explicit concent. Safari is a web browser provided by Apple. Safari installed in iPod touch and iPhone accepts a...

Design/Logic Flaw

WebCore in Apple Safari does not properly perform garbage collection of JavaScript document elements, which allows remote attackers to execute arbitrary code or cause a denial of service heap corruption and application crash via a reference to the ownerNode property of a copied CSSStyleSheet obje...

CVE-2008-1590

JavaScriptCore in WebKit on Apple iPhone before 2.0 and iPod touch before 2.0 does not properly perform runtime garbage collection, which allows remote attackers to execute arbitrary code or cause a denial of service application crash via unspecified vectors that trigger memory corruption, a...

Integer overflow

Integer signedness error in Safari on Apple iPhone before 2.0 and iPod touch before 2.0 allows remote attackers to execute arbitrary code or cause a denial of service application crash via vectors involving JavaScript array indices that trigger an out-of-bounds access, a different vulnerability...

CVE-2008-1588

Safari on Apple iPhone before 2.0 and iPod touch before 2.0 allows remote attackers to spoof the address bar via Unicode ideographic spaces in the URL...

CVE-2008-2303

Integer signedness error in Safari on Apple iPhone before 2.0 and iPod touch before 2.0 allows remote attackers to execute arbitrary code or cause a denial of service application crash via vectors involving JavaScript array indices that trigger an out-of-bounds access, a different vulnerability...

Design/Logic Flaw

Safari on Apple iPhone before 2.0 and iPod touch before 2.0 misinterprets a menu button press as user confirmation for visiting a web site with a 1 self-signed or 2 invalid certificate, which makes it easier for remote attackers to spoof web sites...

Memory corruption

JavaScriptCore in WebKit on Apple iPhone before 2.0 and iPod touch before 2.0 does not properly perform runtime garbage collection, which allows remote attackers to execute arbitrary code or cause a denial of service application crash via unspecified vectors that trigger memory corruption, a...

CVE-2008-1589

Safari on Apple iPhone before 2.0 and iPod touch before 2.0 misinterprets a menu button press as user confirmation for visiting a web site with a 1 self-signed or 2 invalid certificate, which makes it easier for remote attackers to spoof web sites...

CVE-2008-2303

CVE-2008-2303 affects Safari on Apple iPhone before 2.0 and iPod touch before 2.0. It is caused by an integer signedness error in handling JavaScript array indices, which can trigger an out-of-bounds access. The result can be remote arbitrary code execution or a denial of service (application cra...

CVE-2008-2303

Integer signedness error in Safari on Apple iPhone before 2.0 and iPod touch before 2.0 allows remote attackers to execute arbitrary code or cause a denial of service application crash via vectors involving JavaScript array indices that trigger an out-of-bounds access, a different vulnerability...

CVE-2008-1590

CVE-2008-1590 relates to a memory corruption flaw in WebKit/JavaScriptCore on Apple iPhone and iPod touch before version 2.0, caused by improper runtime garbage collection. This can allow a remote attacker to execute arbitrary code or cause an application crash via memory corruption, via unspecif...

CVE-2008-1588

CVE-2008-1588 affects Safari on Apple iPhone before 2.0 and iPod touch before 2.0. The underlying issue lets remote attackers spoof the address bar by using Unicode ideographic spaces in the URL, potentially deceiving users about the site they visit. The vulnerability references indicate affected...

CVE-2008-1589

CVE-2008-1589 affects Safari on Apple iPhone/iPod touch prior to v2.0. The issue: when visiting a site with a self-signed or invalid certificate, pressing the menu button during the certificate prompt can cause the certificate acceptance on the next visit, enabling potential MITM or credential ex...

CVE-2008-1589

Safari on Apple iPhone before 2.0 and iPod touch before 2.0 misinterprets a menu button press as user confirmation for visiting a web site with a 1 self-signed or 2 invalid certificate, which makes it easier for remote attackers to spoof web sites...

JVN#88676089 Safari installed in iPod touch and iPhone vulnerable in handling server certificates

Safari is a web browser provided by Apple. Safari installed in iPod touch and iPhone accepts a self-signed or invalid server cerficate without the user's explicit concent when connecting via SSL/TLS. According to Apple, "When Safari accesses a website that uses a self-signed or invalid certificat...

PT-2008-3146 · Apple · Javascriptcore +3

Name of the Vulnerable Software and Affected Versions: WebKit versions prior to 2.0 on Apple iPhone WebKit versions prior to 2.0 on iPod touch Description: The issue is related to improper runtime garbage collection in JavaScriptCore, which can lead to memory corruption. This can be exploited by...