Vulnerabilidades do Apple Macos
🔔 Criar alerta RSS Verificador de versão
CVEs publicadas que afetam Apple Macos: 1087 registro(s), com versões afetadas e correções.cpe:2.3:o:apple:macos
CVE-2020-14155
Média · 5.3
CWE-190 15/06/2020
Integer Overflow or Wraparound em Pcre
libpcre in PCRE before 8.44 allows an integer overflow via a large number after a (?C substring.
CVE-2019-20838
Alta · 7.5
CWE-125 15/06/2020
Out-of-bounds Read em Pcre
libpcre in PCRE before 8.43 allows a subject buffer over-read in JIT when UTF is disabled, and \X or \R has more than one fixed quantifier, a related issue to CVE-2019-20454.
CVE-2020-9859
Alta · 7.8
KEV Alta · 50 CWE-415 05/06/2020
Apple Multiple Products Code Execution Vulnerability
A memory consumption issue was addressed with improved memory handling. This issue is fixed in iOS 13.5.1 and iPadOS 13.5.1, macOS Catalina 10.15.5 Supplemental Update, tvOS 13.4.6, watchOS 6.2.6. An application may be able to execute arbitrary code with kernel privileges.
CVE-2020-13631
Média · 5.5
27/05/2020
SQLite before 3.32.0 allows a virtual table to be renamed to the name of one of its shadow tables...
SQLite before 3.32.0 allows a virtual table to be renamed to the name of one of its shadow tables, related to alter.c and build.c.
CVE-2020-13630
Alta · 7.0
CWE-416 27/05/2020
ext/fts3/fts3.c in SQLite before 3.32.0 has a use-after-free in fts3EvalNextRow, related to the...
ext/fts3/fts3.c in SQLite before 3.32.0 has a use-after-free in fts3EvalNextRow, related to the snippet feature.
CVE-2020-13434
Média · 5.5
CWE-190 24/05/2020
SQLite through 3.32.0 has an integer overflow in sqlite3_str_vappendf in printf.c.
SQLite through 3.32.0 has an integer overflow in sqlite3_str_vappendf in printf.c.
CVE-2020-3837
Alta · 7.8
KEV Alta · 64 Exploit público CWE-787 27/02/2020
Apple Multiple Products Memory Corruption Vulnerability
A memory corruption issue was addressed with improved memory handling. This issue is fixed in iOS 13.3.1 and iPadOS 13.3.1, macOS Catalina 10.15.3, tvOS 13.3.1, watchOS 6.1.2. An application may be able to execute arbitrary code with kernel privileges.
CVE-2019-8605
Alta · 7.8
KEV Urgente · 70 Exploit público CWE-416 18/12/2019
Apple Multiple Products Use-After-Free Vulnerability
A use after free issue was addressed with improved memory management. This issue is fixed in iOS 12.3, macOS Mojave 10.14.5, tvOS 12.3, watchOS 5.2.1. A malicious application may be able to execute arbitrary code with system privileges.
CVE-2019-8526
Alta · 7.8
KEV Alta · 49 CWE-416 18/12/2019
Apple macOS Use-After-Free Vulnerability
A use after free issue was addressed with improved memory management. This issue is fixed in macOS Mojave 10.14.4. An application may be able to gain elevated privileges.
CVE-2019-7286
Alta · 7.8
KEV Alta · 64 Exploit público CWE-787 18/12/2019
Apple Multiple Products Memory Corruption Vulnerability
A memory corruption issue was addressed with improved input validation. This issue is fixed in iOS 12.1.4, macOS Mojave 10.14.3 Supplemental Update. An application may be able to gain elevated privileges.
CVE-2019-6223
Alta · 7.5
KEV Alta · 54 05/03/2019
Apple iOS and macOS Group Facetime Vulnerability
A logic issue existed in the handling of Group FaceTime calls. The issue was addressed with improved state management. This issue is fixed in iOS 12.1.4, macOS Mojave 10.14.3 Supplemental Update. The initiator of a Group FaceTime call may be able to cause the recipient to answer.
CVE-2013-0340
Média · 6.8
CWE-611 21/01/2014
expat 2.1.0 and earlier does not properly handle entities expansion unless an application...
expat before version 2.4.0 does not properly handle entities expansion unless an application developer uses the XML_SetEntityDeclHandler function, which allows remote attackers to cause a denial of service (resource consumption), send HTTP requests to intranet servers, or read arbitrary files via a crafted XML document, aka an XML External Entity (XXE) issue. NOTE: it could be argued that because expat already provides the ability to disable external entity expansion, the responsibility for resolving this issue lies with application developers; according to this argument, this entry should be REJECTed, and each affected application would need its own CVE.