Arbitrary firmware boot via replaced gunzip
Published Jun 2, 2025 · Updated Jun 3, 2025
Secure boot bypass in ARRIS VIP1113 devices through 2025-05-30 allows local users to boot arbitrary images via a replaced gunzip binary. The second-stage bootloader validates the downloaded image, then invokes /usr/bin/gunzip from a writable filesystem, allowing a replacement binary to modify the image before kexec. Exploitation requires privileged boot-configuration access and a preceding executable-overwrite path; success grants root-level control through attacker-supplied firmware.
Summary
What happened
Secure boot bypass in ARRIS VIP1113 devices through 2025-05-30 allows local users to boot arbitrary images via a replaced gunzip binary. The second-stage bootloader validates the downloaded image, then invokes /usr/bin/gunzip from a writable filesystem, allowing a replacement binary to modify the image before kexec. Exploitation requires privileged boot-configuration access and a preceding executable-overwrite path; success grants root-level control through attacker-supplied firmware.
The record
- CVE
- CVE-2025-49163
- Published
- Jun 2, 2025
- Updated
- Jun 3, 2025
- Vendor
- ARRIS
- Product
- ARRIS VIP1113
- Classifications
- CWE-424, T1542.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 2, 2025CVE publishedPublication date reported by the CVE source.
- Jun 3, 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 <=2025-05-30
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
- TFTP boot-chain proof of conceptproof of concept · demonstrated
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