Apple macOS up to 12.7.5/13.6.7/14.5 File memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Apple macOS up to 12.7.5/13.6.7/14.5. The impacted element is an unknown function of the component File Handler. Performing a manipulation results in memory corruption. This vulnerability is cataloged as CVE-2024-27877. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Apple macOS up to 12.7.5/13.6.7/14.5. This affects an unknown code of the component File Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The issue was addressed with improved memory handling. This issue is fixed in macOS Monterey 12.7.6, macOS Sonoma 14.6, macOS Ventura 13.6.8. Processing a maliciously crafted file may lead to a denial-of-service or potentially disclose memory contents.
The advisory is shared at support.apple.com. This vulnerability is uniquely identified as CVE-2024-27877 since 02/26/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/04/2026).
Upgrading to version 12.7.6, 13.6.8 or 14.6 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 12.7.0
- 12.7.1
- 12.7.2
- 12.7.3
- 12.7.4
- 12.7.5
- 13.6.0
- 13.6.1
- 13.6.2
- 13.6.3
- 13.6.4
- 13.6.5
- 13.6.6
- 13.6.7
- 14.0
- 14.1
- 14.2
- 14.3
- 14.4
- 14.5
License
Website
- Vendor: https://www.apple.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.2VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔍
ADP CISA Base Score: 6.1
ADP CISA Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: macOS 12.7.6/13.6.8/14.6
Timeline
02/26/2024 🔍07/30/2024 🔍
07/30/2024 🔍
04/04/2026 🔍
Sources
Vendor: apple.comAdvisory: support.apple.com
Status: Confirmed
CVE: CVE-2024-27877 (🔍)
GCVE (CVE): GCVE-0-2024-27877
GCVE (VulDB): GCVE-100-272829
scip Labs: https://www.scip.ch/en/?labs.20180712
Entry
Created: 07/30/2024 08:21Updated: 04/04/2026 06:58
Changes: 07/30/2024 08:21 (57), 07/31/2024 05:45 (1), 08/09/2024 19:56 (11), 03/16/2025 16:38 (3), 04/04/2026 06:58 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.