AMF crash via unchecked multipart part count
Published Apr 5, 2022 · Updated Aug 4, 2024
A stack buffer overflow in Open5GS 2.3.6 and earlier allows remote attackers to crash the AMF via a crafted SBI multipart request. The SBI multipart parser increments num_of_part beyond the eight-entry part array and writes attacker-controlled part metadata outside the array. The request reaches the AMF HTTP/2 service without authentication; successful exploitation interrupts the AMF process without reported confidentiality or integrity impact.
Summary
What happened
A stack buffer overflow in Open5GS 2.3.6 and earlier allows remote attackers to crash the AMF via a crafted SBI multipart request. The SBI multipart parser increments num_of_part beyond the eight-entry part array and writes attacker-controlled part metadata outside the array. The request reaches the AMF HTTP/2 service without authentication; successful exploitation interrupts the AMF process without reported confidentiality or integrity impact.
The record
- CVE
- CVE-2021-44109
- Published
- Apr 5, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 5, 2022CVE 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
- Open5GS AMF multipart request crash proof of conceptproof 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