Null pointer dereference in CLI led

[HorizontalCar]

Describe the bug

CLI can call parseLedStripConfig with null argument for config if not enough arguments are passed. The code should check that the return value of nextArg is non-null at:

betaflight/src/main/cli/cli.c

Line 1960 in 660018b

ptr = nextArg(cmdline);

Otherwise result in a null pointer dereference at:

betaflight/src/main/cli/cli.c

Line 1961 in 660018b

if (parseLedStripConfig(i, ptr)) {

To Reproduce

In CLI mode:

Entering CLI Mode, type 'exit' to return, or 'help'

# led +

Expected behavior

Does not crash on incorrect use of CLI led

Support ID

N/A

Flight controller

N/A

Other components

No response

How are the different components wired up (including port information)

No response

Add any other context about the problem that you think might be relevant here

I've been testing automated firmware testing tools on Betaflight firmware, so I am not using the firmware directly. Instead, I am emulating it in a testing environment and manually triaging the crashes I find. During my testing, I found inputs that trigger a null pointer dereference in CLI mode.

[haslinghuis]

Result:

# led +
###ERROR IN led: PARSING FAILED###