SSMC and log4j vulnerability

[sbhat09]

Hello @ArjanSchepers,

I am not allowed to share the workaround publicly. But the security update patch to address 'log4j' vulnerability is in progress and will be released soon.

Till then you can shut-down the SSMC. Use CLI for important administration tasks.

If that is not an option for you, I can personal message you the steps of temporary workaround.

How do you like to go about this?

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.

[ArjanSchepers]

Hello @sbhat09 , if you could PM me the workaround instructions, that would be great. Thank you in advance!

[jvbakel]

Hello, would you be able to send me the workaround instructions as well per DM? We shut our SSMCs down, and really need them up.

[sbhat09]

Hello @jvbakel,

Sent it.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.

[sbhat09]

Hello @ArjanSchepers ,

Sent it.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.

[aireynol]

Please PM it to me also.

[Alex781]

Hi,
we still use the old windows software based SSMC 3.3.1 which seems also to be affected by log4j issue.
Is there any chance that HPE will provide an update or at least a workaround for this old version, or do we need to migrate to the SSMC VM appliance?
Thx & regards
Alex

[karla87]

Hello @sbhat09

Could you please PM me the workaround as well. 

Thanks for your help!

[sbhat09]

Hello @aireynol @karla87 

Sent it.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.

[jeff07]

Hi Srinivas, can you please share the workaround via PM?  Thanks!