Unauthenticated adjacent RCE via filename extension overflow
Published Feb 18, 2022 · Updated Aug 3, 2024
A stack-based buffer overflow in TP-Link TL-WR940N 3.20.1 Build 200316 Rel.34392n (5553) allows remote attackers to execute arbitrary code via network-adjacent requests. The httpd httpRpmFs filename-extension parser copies length-unvalidated input into a fixed-size stack buffer. No authentication is required, and successful exploitation executes code as root, enabling complete router compromise.
Summary
What happened
A stack-based buffer overflow in TP-Link TL-WR940N 3.20.1 Build 200316 Rel.34392n (5553) allows remote attackers to execute arbitrary code via network-adjacent requests. The httpd httpRpmFs filename-extension parser copies length-unvalidated input into a fixed-size stack buffer. No authentication is required, and successful exploitation executes code as root, enabling complete router compromise.
The record
- CVE
- CVE-2022-24355
- Published
- Feb 18, 2022
- Updated
- Aug 3, 2024
- Vendor
- TP-Link
- Product
- TL-WR940N
- Classifications
- CWE-787, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=3.20.1 Build 200316 Rel.34392n (5553)
What conditions does exploitation require?
What is affected?
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
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