OneMesh function crash via malformed tdpServer input
Published Dec 7, 2022 · Updated Apr 23, 2025
Improper input handling in TP-Link RE300 V1 firmware before 221009 allows attackers to crash the OneMesh function. Public records identify tdpServer as the locus but do not disclose the malformed input or failing operation that triggers the crash. Exploitation requires adjacent-network access, needs no authentication or user interaction, and interrupts OneMesh rather than the entire device.
Summary
What happened
Improper input handling in TP-Link RE300 V1 firmware before 221009 allows attackers to crash the OneMesh function. Public records identify tdpServer as the locus but do not disclose the malformed input or failing operation that triggers the crash. Exploitation requires adjacent-network access, needs no authentication or user interaction, and interrupts OneMesh rather than the entire device.
The record
- CVE
- CVE-2022-41783
- Published
- Dec 7, 2022
- Updated
- Apr 23, 2025
- Vendor
- TP-Link
- Product
- TP-Link RE300
- Classifications
- CWE-228, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 7, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=firmware versions prior to 221009
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.
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