Unauthenticated memory corruption via setbg_num stack overflow
Published Dec 30, 2022 · Updated Apr 11, 2025
Stack-based buffer overflow in TRENDnet TEW-755AP firmware 1.13B01 allows remote attackers to corrupt memory via a crafted setbg_num value. The icp_setbg_img function accepts the unbounded parameter and writes beyond a stack buffer in the device firmware. No authentication or user interaction is required, but public evidence does not establish a repeatable consequence beyond memory corruption.
Summary
What happened
Stack-based buffer overflow in TRENDnet TEW-755AP firmware 1.13B01 allows remote attackers to corrupt memory via a crafted setbg_num value. The icp_setbg_img function accepts the unbounded parameter and writes beyond a stack buffer in the device firmware. No authentication or user interaction is required, but public evidence does not establish a repeatable consequence beyond memory corruption.
The record
- CVE
- CVE-2022-46601
- 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
- Vul7 TEW755 icp_setbg_img proof of conceptproof 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