Memory corruption via unchecked MAC-filter comment
Published May 8, 2025 · Updated May 12, 2025
Buffer overflow in setMacFilterRules in TOTOLINK A3100R firmware 5.9c.1527 allows remote attackers to corrupt memory via a crafted comment parameter. The handler fails to enforce destination-buffer bounds when processing the attacker-controlled comment value. Network access without authentication or user interaction is sufficient, but public evidence establishes neither a specific crash nor code execution.
Summary
What happened
Buffer overflow in setMacFilterRules in TOTOLINK A3100R firmware 5.9c.1527 allows remote attackers to corrupt memory via a crafted comment parameter. The handler fails to enforce destination-buffer bounds when processing the attacker-controlled comment value. Network access without authentication or user interaction is sufficient, but public evidence establishes neither a specific crash nor code execution.
The record
- CVE
- CVE-2025-45788
- Published
- May 8, 2025
- Updated
- May 12, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-121, CWE-787, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 8, 2025CVE publishedPublication date reported by the CVE source.
- May 12, 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.
Weakness, pattern, technique
Public exploit references
- A3100R-2 public 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