SMF crash via undersized PFCP index allocation
Published Jul 16, 2024 · Updated Aug 2, 2024
Heap-based buffer overflow in Open5GS 2.6.4 causes an out-of-bounds write during SMF PFCP context initialization. The pdr_random_to_index array is allocated for pool.size entries, but initialization indexes it with one-based randomized TEID pool values that can equal pool.size. The flaw occurs when the SMF starts; AddressSanitizer demonstrates a four-byte heap write and abort, while noninstrumented consequences are not documented.
Summary
What happened
Heap-based buffer overflow in Open5GS 2.6.4 causes an out-of-bounds write during SMF PFCP context initialization. The pdr_random_to_index array is allocated for pool.size entries, but initialization indexes it with one-based randomized TEID pool values that can equal pool.size. The flaw occurs when the SMF starts; AddressSanitizer demonstrates a four-byte heap write and abort, while noninstrumented consequences are not documented.
The record
- CVE
- CVE-2024-40129
- Published
- Jul 16, 2024
- Updated
- Aug 2, 2024
- Vendor
- Open5GS
- Product
- Open5GS
- Classifications
- CWE-122, CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 16, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.4
What conditions does exploitation require?
What is affected?
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
- ASan SMF startup reproducerproof 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