Unverified update installation via mutable verified archive
Published Feb 4, 2025 · Updated Feb 17, 2025
Archive verification bypass in Sparkle before 2.6.4 allows attackers to install a substituted update payload on macOS. The updater keeps the verified input archive in its writable extraction directory, allowing replacement after signature validation and before extraction completes. Exploitation requires high privileges and access to the update workflow, and the substituted payload executes when the host application installs the update.
Summary
What happened
Archive verification bypass in Sparkle before 2.6.4 allows attackers to install a substituted update payload on macOS. The updater keeps the verified input archive in its writable extraction directory, allowing replacement after signature validation and before extraction completes. Exploitation requires high privileges and access to the update workflow, and the substituted payload executes when the host application installs the update.
The record
- CVE
- CVE-2025-0509
- Published
- Feb 4, 2025
- Updated
- Feb 17, 2025
- Vendor
- Sparkle Project
- Product
- Sparkle
- Classifications
- CWE-552, T1553
- Attack vector
- adjacent
- Privileges
- admin
Timeline
How it unfolded
- Feb 4, 2025CVE publishedPublication date reported by the CVE source.
- Feb 17, 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=0 <2.6.4
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.
Weakness, pattern, technique
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