Local denial-of-service via improper libc input validation
Published Sep 15, 2025 · Updated Sep 15, 2025
Improper input validation in Apple libc allows local users to cause a denial-of-service through an app on affected iOS, iPadOS, and macOS releases. The libc flaw accepts an undisclosed form of invalid input instead of rejecting it; Apple has not identified the function, input format, or failure mode. User interaction is required, and Apple has not disclosed whether the resulting service interruption is a hang, crash, or broader system failure.
Summary
What happened
Improper input validation in Apple libc allows local users to cause a denial-of-service through an app on affected iOS, iPadOS, and macOS releases. The libc flaw accepts an undisclosed form of invalid input instead of rejecting it; Apple has not identified the function, input format, or failure mode. User interaction is required, and Apple has not disclosed whether the resulting service interruption is a hang, crash, or broader system failure.
The record
- CVE
- CVE-2025-43299
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-20, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <18.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo