Pre-authentication memory corruption via oversized POST data
Published Nov 23, 2022 · Updated Apr 25, 2025
A pre-authentication buffer overflow in TOTOLINK LR350 firmware 9.3.5u.6369_B20220309 allows remote attackers to corrupt memory via long POST data. The firmware's main function processes oversized POST content without keeping the write within the destination buffer. No credentials or user interaction are required, and published evidence does not establish whether the corruption causes only a crash or enables code execution.
Summary
What happened
A pre-authentication buffer overflow in TOTOLINK LR350 firmware 9.3.5u.6369_B20220309 allows remote attackers to corrupt memory via long POST data. The firmware's main function processes oversized POST content without keeping the write within the destination buffer. No credentials or user interaction are required, and published evidence does not establish whether the corruption causes only a crash or enables code execution.
The record
- CVE
- CVE-2022-44255
- Published
- Nov 23, 2022
- Updated
- Apr 25, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 23, 2022CVE publishedPublication date reported by the CVE source.
- Apr 25, 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
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