CVE-2024-44258: CVE-2024-44258: This issue was addressed with improved handling of symlinks. This issue is fixed in iOS 17…
apple · ipados · NVD published 2024-10-29 · posted 2024-10-29 · last modified 2026-06-17
What it is
This issue was addressed with improved handling of symlinks. This issue is fixed in iOS 17.7.1 and iPadOS 17.7.1, iOS 18.1 and iPadOS 18.1, tvOS 18.1, visionOS 2.1. Restoring a maliciously crafted backup file may lead to modification of protected system files.
| Weakness | CWE-59 |
|---|---|
| CVSS vector | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H (source: [email protected]) |
| ATT&CK tactics | n/a |
Exploitation evidence
First exploit evidence seen: 2024-10-29 (earliest date across the sources below).
Exploited in the wild
No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).
Public exploit code
GitHub proof-of-concept repositories
2 public repositories from 2 accounts, first seen 2024-10-29. Most starred: ifpdz/CVE-2024-44258 (87 stars), view repository.
Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.
Sources: nomi-sec/PoC-in-GitHub.
How to fix it
Fixed versions
- apple ipados: upgrade to 17.7.1 or later
- apple ipados: upgrade to 18.1 or later (affected from 18.0)
- apple iphone os: upgrade to 17.7.1 or later
- apple iphone os: upgrade to 18.1 or later (affected from 18.0)
- apple tvos: upgrade to 18.1 or later
- apple visionos: upgrade to 2.1 or later
Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.
Vendor advisories and patches
- https://support.apple.com/en-us/121563 (Release Notes, Vendor Advisory)
- https://support.apple.com/en-us/121566 (Release Notes, Vendor Advisory)
- https://support.apple.com/en-us/121567 (Release Notes, Vendor Advisory)
- https://support.apple.com/en-us/121569 (Release Notes, Vendor Advisory)
Detection Generic guidance
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.