Authenticated memory corruption via unbounded service_type parameter
Published Apr 27, 2025 · Updated Apr 28, 2025
Buffer overflow in TOTOLINK N150RT 3.4.0-B20190525 allows remote authenticated users to corrupt memory via a crafted HTTP POST request. The /boafrm/formPortFw handler fails to bound the service_type body parameter before processing it, causing the overflow. Valid router credentials are required, and exploitation can corrupt router memory; no more specific runtime consequence is published.
Summary
What happened
Buffer overflow in TOTOLINK N150RT 3.4.0-B20190525 allows remote authenticated users to corrupt memory via a crafted HTTP POST request. The /boafrm/formPortFw handler fails to bound the service_type body parameter before processing it, causing the overflow. Valid router credentials are required, and exploitation can corrupt router memory; no more specific runtime consequence is published.
The record
- CVE
- CVE-2025-3988
- Published
- Apr 27, 2025
- Updated
- Apr 28, 2025
- Vendor
- TOTOLINK
- Product
- N150RT
- Classifications
- CWE-120, CWE-119, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 27, 2025CVE publishedPublication date reported by the CVE source.
- Apr 28, 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=3.4.0-B20190525
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
- N150RT formPortFw proof of conceptproof of concept · unverified
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