Memory corruption via unchecked firmware filename
Published Dec 30, 2022 · Updated Apr 11, 2025
Stack overflow in TRENDnet TEW-755AP 1.13B01 allows remote attackers to corrupt memory via a crafted firmware filename. The auto_up_fw function processes the attacker-controlled update_file_name parameter without adequate bounds checking, causing a write beyond its stack buffer. No authentication or user interaction is required, and public evidence establishes memory corruption but not a specific code-execution outcome.
Summary
What happened
Stack overflow in TRENDnet TEW-755AP 1.13B01 allows remote attackers to corrupt memory via a crafted firmware filename. The auto_up_fw function processes the attacker-controlled update_file_name parameter without adequate bounds checking, causing a write beyond its stack buffer. No authentication or user interaction is required, and public evidence establishes memory corruption but not a specific code-execution outcome.
The record
- CVE
- CVE-2022-46594
- Published
- Dec 30, 2022
- Updated
- Apr 11, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 30, 2022CVE publishedPublication date reported by the CVE source.
- Apr 11, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Vul1 TEW755 bof auto_up_fwproof of concept · unverified
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