Описание
A client holding only a read JWT scope can still register itself as a signal provider through the production kuksa.val.v2 OpenProviderStream API by sending ProvideSignalRequest.
- Obtain any valid token with only read scope.
- Connect to the normal production gRPC API (kuksa.val.v2).
- Open OpenProviderStream.
- Send ProvideSignalRequest for a target signal ID.
- Wait for the broker to forward GetProviderValueRequest.
- Reply with attacker-controlled GetProviderValueResponse.
- Other clients performing GetValue / GetValues for that signal receive forged data.
A client holding only a read JWT scope can still register itself as a signal provider through the production kuksa.val.v2 OpenProviderStream API by sending ProvideSignalRequest.
- Obtain any valid token with only read scope.
- Connect to the normal production gRPC API (kuksa.val.v2).
- Open OpenProviderStream.
- Send ProvideSignalRequest for a target signal ID.
- Wait for the broker to forward GetProviderValueRequest.
- Reply with attacker-controlled GetProviderValueResponse.
- Other clients performing GetValue / GetValues for that signal receive forged data.
Связанные уязвимости
A client holding only a read JWT scope can still register itself as a signal provider through the production kuksa.val.v2 OpenProviderStream API by sending ProvideSignalRequest. 1. Obtain any valid token with only read scope. 2. Connect to the normal production gRPC API (kuksa.val.v2). 3. Open OpenProviderStream. 4. Send ProvideSignalRequest for a target signal ID. 5. Wait for the broker to forward GetProviderValueRequest. 6. Reply with attacker-controlled GetProviderValueResponse. 7. Other clients performing GetValue / GetValues for that signal receive forged data.