Unauthenticated memory corruption via oversized picName
Published Dec 23, 2022 · Updated Apr 15, 2025
A buffer overflow in IP-COM M50 15.11.0.33(10768) allows remote attackers to corrupt process memory through a crafted picName parameter. The formDelWewifiPic handler copies picName into a fixed-size destination without validating its length, overflowing the destination buffer. No authentication or user interaction is required; public evidence demonstrates the overflow but does not establish a specific post-corruption outcome.
Summary
What happened
A buffer overflow in IP-COM M50 15.11.0.33(10768) allows remote attackers to corrupt process memory through a crafted picName parameter. The formDelWewifiPic handler copies picName into a fixed-size destination without validating its length, overflowing the destination buffer. No authentication or user interaction is required; public evidence demonstrates the overflow but does not establish a specific post-corruption outcome.
The record
- CVE
- CVE-2022-45721
- Published
- Dec 23, 2022
- Updated
- Apr 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 23, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 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
- IP-COM M50 formDelWewifiPic 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