Unauthenticated code execution via stack buffer overflow
Published Feb 22, 2022 · Updated Aug 3, 2024
Stack-based buffer overflow in TP-Link Archer A54 firmware 210111 allows remote attackers to execute arbitrary code via an HTTP request. The DM_Fillobjbystr function insufficiently sanitizes user-supplied request data before writing it to a stack buffer, allowing the write to exceed the buffer boundary. No authentication or user interaction is required, and successful exploitation permits code execution in the router application's context.
Summary
What happened
Stack-based buffer overflow in TP-Link Archer A54 firmware 210111 allows remote attackers to execute arbitrary code via an HTTP request. The DM_Fillobjbystr function insufficiently sanitizes user-supplied request data before writing it to a stack buffer, allowing the write to exceed the buffer boundary. No authentication or user interaction is required, and successful exploitation permits code execution in the router application's context.
The record
- CVE
- CVE-2022-25072
- Published
- Feb 22, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 22, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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