Command execution via crafted firmware filename
Published May 28, 2024 · Updated Jul 9, 2026
Command injection in TOTOLINK CP900L firmware 4.1.5cu.798_B20221228 allows local users to execute commands via a crafted firmware filename. UploadFirmwareFile incorporates the attacker-controlled FileName value into an operating-system command without neutralizing command syntax. Local access to the firmware-upload path is required, and injected commands can read or alter device data and interrupt service.
Summary
What happened
Command injection in TOTOLINK CP900L firmware 4.1.5cu.798_B20221228 allows local users to execute commands via a crafted firmware filename. UploadFirmwareFile incorporates the attacker-controlled FileName value into an operating-system command without neutralizing command syntax. Local access to the firmware-upload path is required, and injected commands can read or alter device data and interrupt service.
The record
- CVE
- CVE-2024-35401
- Published
- May 28, 2024
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-77, T1059
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2024CVE publishedPublication date reported by the CVE source.
- Jul 9, 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.
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