SMF goes into a heartbeattimer busy loop when NRF profile response could not be read
Issue
When NF instance registration response data could not be parsed, or there is an error, this error is not handled correctly (smf_sbi.cpp
line 483 following (for new HTTP client config)).
This leads to the issue that the heartbeat timer in NF profile is set to 0, which results in a busy loop for the
Possible implications
- SMF becomes unusable
- Network may get delayed
- Attacker could intercept these messages and just remove the body, which leads to an SMF "busy loop"
Possible Solution
Implement a validation (for these error cases but also for API input in general) to set the heartbeat value to a minimum level (e.g. 5 seconds)