{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65567 exists.","fix":"No fix has been published for CVE-2025-65567 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-65567 is a high-severity denial of service vulnerability in n/a, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-65567 and fix it if it is affected.\n\nWhat it is: CVE-2025-65567 is a high-severity denial of service vulnerability in n/a, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65567 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-65567/ (Markdown: https://insights.sbomify.com/CVE-2025-65567/index.md)","id":"CVE-2025-65567","markdown":"https://insights.sbomify.com/CVE-2025-65567/index.md","name":"CVE-2025-65567","record":{"aliases":["GHSA-w3v7-wwmg-2j8p"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"5G Core UPF","requires_auth":"none","summary":"An attacker can crash the UPF process by sending a malformed PFCP Session Establishment Request, causing a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"upf","vendor":"opennetworking"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"A denial-of-service vulnerability exists in the omec-project UPF (pfcpiface component) in version upf-epc-pfcpiface:2.1.3-dev. After PFCP association, a specially crafted PFCP Session Establishment Request with a CreatePDR that contains a malformed Flow-Description is not robustly validated. The Flow-Description parser (parseFlowDesc) can read beyond the bounds of the provided buffer, causing a panic and terminating the UPF process. An attacker who can send PFCP Session Establishment Request messages to the UPF's N4/PFCP endpoint can exploit this issue to repeatedly crash the UPF.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Denial of service in n/a","id":"CVE-2025-65567","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2025-65568"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2025-65566"},"products":["n/a"],"published":"2025-12-18","related":[{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2025-65563","kev_date_added":null,"published":"2025-12-18"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2025-65564","kev_date_added":null,"published":"2025-12-18"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2025-65565","kev_date_added":null,"published":"2025-12-18"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2025-65568","kev_date_added":null,"published":"2025-12-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-19","vendors":["n/a"]},"summary":"An attacker can crash the UPF process by sending a malformed PFCP Session Establishment Request, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2025-65567/"}