Authenticated stack corruption via unchecked Diameter counts
Published Aug 12, 2026 · Updated Aug 12, 2026
Stack buffer overflow in Open5GS 2.7.0 through 2.7.1 allows remote authenticated users to corrupt PCRF memory via a Diameter Rx AAR. The pcrf_rx_aar_cb callback indexes fixed stack arrays with unchecked media-component and subcomponent counters from nested AVPs. A connected Diameter peer and an attached subscriber are required; the public packet capture demonstrates controlled four-byte stack writes.
Summary
What happened
Stack buffer overflow in Open5GS 2.7.0 through 2.7.1 allows remote authenticated users to corrupt PCRF memory via a Diameter Rx AAR. The pcrf_rx_aar_cb callback indexes fixed stack arrays with unchecked media-component and subcomponent counters from nested AVPs. A connected Diameter peer and an attached subscriber are required; the public packet capture demonstrates controlled four-byte stack writes.
The record
- CVE
- CVE-2024-14044
- Published
- Aug 12, 2026
- Updated
- Aug 12, 2026
- Vendor
- Open5GS
- Product
- Open5GS
- Classifications
- CWE-119, CWE-120, T1210
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 2026CVE publishedPublication date reported by the CVE source.
- Aug 12, 2026Record 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.7.0
- Affected versionversion=2.7.1
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.
Weakness, pattern, technique
Public exploit references
- Offending Diameter Rx AAR packet captureproof 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