CVE-2007-4682
published 2007-11-15CVE-2007-4682: CoreText in Apple Mac OS X 10.4 through 10.4.10 allows attackers to cause a denial of service (application crash) and possibly execute arbitrary code via…
PriorityP423medium6.8CVSS 2.0
AVNACMAuNCPIPAP
EPSS
3.21%
86.9th percentile
CoreText in Apple Mac OS X 10.4 through 10.4.10 allows attackers to cause a denial of service (application crash) and possibly execute arbitrary code via crafted text content that triggers an access of an uninitialized object pointer.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| apple | mac_os_x | 10.4 – 10.4.10 | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
CWE
Access of Uninitialized Pointer
mitre_cwe
CWE-824 Access of Uninitialized Pointer
CWE-824: Access of Uninitialized Pointer
The product accesses or uses a pointer that has not been initialized.
If the pointer contains an uninitialized value, then the value might not point to a valid memory location. This could cause the product to read from or write to unexpected memory locations, leading to a denial of service. If the uninitialized pointer is used as a function call, then arbitrary functions could be invoked. If an attacker can influence the portion of uninitialized memory that is contained in the pointer, this weakness could be leveraged to execute code or perform other attacks. Depending on memory layout, associated memory management behaviors, and product operation, the attacker might be able to influence the contents of the uninitialized pointer, thus gaining more
CWE
Use of Uninitialized Variable
mitre_cwe
CWE-457 Use of Uninitialized Variable
CWE-457: Use of Uninitialized Variable
The code uses a variable that has not been initialized, leading to unpredictable or unintended results.
In some languages such as C and C++, stack variables are not initialized by default. They generally contain junk data with the contents of stack memory before the function was invoked. An attacker can sometimes control or read these contents. In other languages or conditions, a variable that is not explicitly initialized can be given a default value that has security implications, depending on the logic of the program. The presence of an uninitialized variable can sometimes indicate a typographic error in the code.
Modes of Introduction:
Phase: Implementation
Note: In C, using an uninitialized char * in some string libraries will return incorrect
http://docs.info.apple.com/article.html?artnum=307041http://lists.apple.com/archives/security-announce/2007/Nov/msg00002.htmlhttp://secunia.com/advisories/27643http://securitytracker.com/id?1018950http://www.kb.cert.org/vuls/id/498105http://www.securityfocus.com/bid/26444http://www.us-cert.gov/cas/techalerts/TA07-319A.htmlhttp://www.vupen.com/english/advisories/2007/3868https://exchange.xforce.ibmcloud.com/vulnerabilities/38465http://docs.info.apple.com/article.html?artnum=307041http://lists.apple.com/archives/security-announce/2007/Nov/msg00002.htmlhttp://secunia.com/advisories/27643http://securitytracker.com/id?1018950http://www.kb.cert.org/vuls/id/498105http://www.securityfocus.com/bid/26444http://www.us-cert.gov/cas/techalerts/TA07-319A.htmlhttp://www.vupen.com/english/advisories/2007/3868https://exchange.xforce.ibmcloud.com/vulnerabilities/38465
2007-11-15
Published