Client crash via heap buffer underwrite
Published Sep 30, 2021 · Updated Aug 4, 2024
Heap-buffer overflow in libiec_iccp_mod 1.5 allows remote attackers to crash an MMS client through a crafted ICCP packet sequence. The MmsConnection_create path allocates a 16,100-byte heap region, after which a 127-byte operation writes one byte before that allocation. Triggering requires client participation in a stateful exchange; the demonstrated consequence is a sanitizer-detected crash, not code execution.
Summary
What happened
Heap-buffer overflow in libiec_iccp_mod 1.5 allows remote attackers to crash an MMS client through a crafted ICCP packet sequence. The MmsConnection_create path allocates a 16,100-byte heap region, after which a 127-byte operation writes one byte before that allocation. Triggering requires client participation in a stateful exchange; the demonstrated consequence is a sanitizer-detected crash, not code execution.
The record
- CVE
- CVE-2020-20663
- Published
- Sep 30, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 30, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
Public exploit references
- mms_client_example1 crash inputproof of concept · demonstrated
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