Enviar #808514: Open5gs NRF v2.7.6 Denial of Service

### Open5GS Release, Revision, or Tag

v2.7.7

### Steps to reproduce

### Description

NRF crashes when a client sends `PUT /nnrf-nfm/v1/nf-instances` without the
required `{nfInstanceId}` path component.

In the NRF state machine, the `PUT` path under `nf-instances` does not verify
that `message.h.resource.component[1]` is present before creating a new local
NF instance and calling:

```c
ogs_sbi_nf_instance_set_id(nf_instance, message.h.resource.component[1]);
```

The setter immediately asserts that the ID pointer is non-NULL:

```c
ogs_assert(id);
```

As a result, a bodyless or otherwise syntactically valid `PUT` to
`/nnrf-nfm/v1/nf-instances` triggers an assertion abort before NRF reaches the
normal registration handler.

### Steps to reproduce

```bash
curl --http2-prior-knowledge -m 5 -sS -i \
-X PUT http://10.33.33.3/nnrf-nfm/v1/nf-instances
```

Then check:

```bash
docker inspect -f '{{.State.Status}} {{.State.ExitCode}} {{.State.FinishedAt}}' nrf
docker logs --tail 20 nrf
```

### Logs

```shell
curl: (56) Recv failure: Connection reset by peer

exited 139 2026-04-10T17:48:02.727465904Z

04/10 17:48:02.618: [sbi] FATAL: ogs_sbi_nf_instance_set_id: Assertion `id' failed. (../lib/sbi/context.c:1259)
```

### Expected behaviour

NRF should reject `PUT /nnrf-nfm/v1/nf-instances` without a path ID with a normal client error such as `400 Bad Request` or `405 Method Not Allowed`.

### Observed Behaviour

The connection is reset and the NRF process exits with code `139`.

### eNodeB/gNodeB

Not required.

### UE Models and versions

Not required.

• Fuente: ⚠️ https://github.com/open5gs/open5gs/issues/4462
• Usuario: LinJu (UID 97503)
• Sumisión: 2026-04-20 21:53 (hace 2 meses)
• Moderación: 2026-05-16 12:09 (26 days later)
• Estado: Aceptado
• Entrada de VulDB: 364319 [Open5GS hasta 2.7.6 NRF /lib/sbi/context.c ogs_sbi_nf_instance_set_id nfInstanceId denegación de servicio]
• Puntos: 20