Firmware disclosure via unauthenticated update endpoints
Published Oct 11, 2024 · Updated Jul 5, 2026
Incorrect authorization in GIANT MANUFACTURING CO., LTD. RideLink 2.0.7 allows remote attackers to download device firmware. The firmware server accepts unauthenticated GET requests to updateinfo.json and returns metadata containing direct ZIP links. No account or device identifier is required; a direct request discloses five firmware images for offline analysis or modification.
Summary
What happened
Incorrect authorization in GIANT MANUFACTURING CO., LTD. RideLink 2.0.7 allows remote attackers to download device firmware. The firmware server accepts unauthenticated GET requests to updateinfo.json and returns metadata containing direct ZIP links. No account or device identifier is required; a direct request discloses five firmware images for offline analysis or modification.
The record
- CVE
- CVE-2024-48778
- Published
- Oct 11, 2024
- Updated
- Jul 5, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1213
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 11, 2024CVE publishedPublication date reported by the CVE source.
- Jul 5, 2026Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Direct firmware download reproductionfunctional · 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