UEFI Redfish Client - exclusive access to resources

ueliyahu
Minnow

Posts: 9

UEFI Redfish Client - exclusive access to resources Jul 9, 2023 6:50:49 GMT

Quote

Post by ueliyahu on Jul 9, 2023 6:50:49 GMT

Hi

At present, the bootstrap account/session creation provides credentials which can be used to access all the Redfish Resources/URL's.
This is shared with BIOS/UEFI Redfish Client so that it will aid in management of a system via BMC Redfish server.
Since these credentials can be used to access any Redfish URL, it can be used by a rogue/malicious UEFI to access the Redfish resources of other systems being managed by the BMC.
This leads to security breach as critical data of other systems is now exposed and can be exploited by malicious UEFI.
Ideally, each UEFI Redfish Client should be given exclusive access to its designated resources only, without the ability to interfere/access other systems being managed by the BMC.

Are there any standard solutions to avoid the issue ?
Thanks !

mraineri
Administrator

Posts: 1,054

UEFI Redfish Client - exclusive access to resources Jul 12, 2023 13:00:34 GMT

Quote

Post by mraineri on Jul 12, 2023 13:00:34 GMT

The only method in place now would be to leverage the "Client certificate authentication" clause in the Redfish spec. The current state of it would likely impact general usage of the system as well, so we might want something more focused client identity certificates installed on the HostInterface resource as a way of enforcing additional verification for these use cases. However, that could lead to provisioning problems where UEFI will need to have a unique certificate with a protected private key, and have the certificate installed on the BMC as well. Beyond using certificates to verify the user, I'm not aware of other possible paths.

ratagupt
Guppy

Posts: 87

UEFI Redfish Client - exclusive access to resources Jul 13, 2023 13:00:59 GMT

Quote

Post by ratagupt on Jul 13, 2023 13:00:59 GMT

@mike @uri: when we say "rogue/malicious UEFI(Rf Client)" can access the resources of other system managed by this BMC?

Are we saying that credentials has been compromised? if yes then whether it is a password based or certificate based authentication, How it is going to help?

If credentials has been compromised and the session has the admin privileges, then it can access all the redfish resources(i.e all the systems under /redfish/v1/Systems/).

>Ideally, each UEFI Redfish Client should be given exclusive access to its designated resources only, without the ability to interfere/access other systems being managed by the BMC.

I am not sure how is it possible.

Client 1 can access the /redfish/v1/Systems/system1 but not the /redfish/v1/Systems/system2.

@mike : Can you describe more what was your thought process?

mraineri
Administrator

Posts: 1,054

UEFI Redfish Client - exclusive access to resources Jul 13, 2023 14:27:02 GMT

Quote

Post by mraineri on Jul 13, 2023 14:27:02 GMT

In this case, if a malicious actor has access to the KCS interface, it can invoke the "Get Bootstrap Credentials" command to get a set of credentials for the service. The credentials themselves aren't necessarily compromised.

I'm thinking the secure flow would be:

Identity certificates are provisioned for UEFI
The same identity certificates are installed on the BMC
UEFI issues the Get Bootstrap Credentials command to get their username and password
UEFI creates a Redfish session with the BMC with the provided username and password; in addition, UEFI provides its identity certificate during TLS handshaking