UPF crash via unchecked PFCP slice bounds
Published Nov 15, 2023 · Updated Aug 29, 2024
Buffer overflow in the free5GC UPF 3.3.0 allows remote attackers to crash the service with a malformed PFCP Heartbeat Request. In the go-pfcp IE.UnmarshalBinary path, unchecked slice bounds on the malformed input produce a slice-bounds runtime panic. No authentication or special configuration is required; successful exploitation terminates the UPF and interrupts packet forwarding.
Summary
What happened
Buffer overflow in the free5GC UPF 3.3.0 allows remote attackers to crash the service with a malformed PFCP Heartbeat Request. In the go-pfcp IE.UnmarshalBinary path, unchecked slice bounds on the malformed input produce a slice-bounds runtime panic. No authentication or special configuration is required; successful exploitation terminates the UPF and interrupts packet forwarding.
The record
- CVE
- CVE-2023-47347
- Published
- Nov 15, 2023
- Updated
- Aug 29, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 15, 2023CVE publishedPublication date reported by the CVE source.
- Aug 29, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- PFCP Heartbeat Request crash proof of conceptfunctional · 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