Unauthenticated code execution via conn-indicator stack overflow
Published May 20, 2025 · Updated May 20, 2025
Stack-based buffer overflow in TP-Link Archer AX50 firmware before 1.0.15 build 241203 rel61480 allows remote attackers to execute code. INCIBE identifies the root-running conn-indicator binary as the locus but does not disclose the triggering input or unsafe memory operation. No authentication or user interaction is required, and crafted traffic reaching the router over a LAN or WAN can yield root-level device control.
Summary
What happened
Stack-based buffer overflow in TP-Link Archer AX50 firmware before 1.0.15 build 241203 rel61480 allows remote attackers to execute code. INCIBE identifies the root-running conn-indicator binary as the locus but does not disclose the triggering input or unsafe memory operation. No authentication or user interaction is required, and crafted traffic reaching the router over a LAN or WAN can yield root-level device control.
The record
- CVE
- CVE-2025-40634
- Published
- May 20, 2025
- Updated
- May 20, 2025
- Vendor
- TP-Link
- Product
- Archer AX50
- Classifications
- CWE-121, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 20, 2025CVE publishedPublication date reported by the CVE source.
- May 20, 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=0 <1.0.15 build 241203 rel61480
What conditions does exploitation require?
What is affected?
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.
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