Memory corruption via MediaServer.exe buffer overflow
Published Apr 29, 2022 · Updated Aug 3, 2024
A buffer overflow in ALLMediaServer 1.6 allows remote attackers to corrupt memory through MediaServer.exe via network requests. Public records identify the executable but do not disclose the input field, protocol message, or unchecked copy operation that overruns the buffer. Network access requires no authentication or user interaction; reliable code execution or service-crash behavior is not publicly detailed.
Summary
What happened
A buffer overflow in ALLMediaServer 1.6 allows remote attackers to corrupt memory through MediaServer.exe via network requests. Public records identify the executable but do not disclose the input field, protocol message, or unchecked copy operation that overruns the buffer. Network access requires no authentication or user interaction; reliable code execution or service-crash behavior is not publicly detailed.
The record
- CVE
- CVE-2022-28480
- Published
- Apr 29, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 29, 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.
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
- ALLMediaServer 1.6 Remote Buffer Overflowproof 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