During startup, stcube prints a message about log4j. There are known vulnrerabilities about log4j. How does this impact stcube and the host system, stcube runs on?
It will try to format the log message and if you have certain patterns in the message being logged, it will load an arbitrary file from a web address to do so. So if you can control what is being logged, perhaps if the program logs user input, you're toast.
It is amazing that a program ostensibly designed to log events in a program has gone through so much feature creep that it is even possible for this to happen. I'm not surprised it happened in Java.
> It is amazing that a program ostensibly designed to log events in a program has gone through so much feature creep
That is also the past and future of the CubeMX. It started as a Microcontroller eXplorer and helped managing pins and clocks. Then the "initialization code generator" was added. Officially it's still called like that! But in reality it has gone down the full - "I'm clicking a project together completely in CubeMX. Something doesn't work. I no learn C. Help!!! Thank you, ser!" - mode. And even sane users want more and more customization. Initialization order, priorities, enable/disable by default etc. Eventually it will mimic all of the HAL in a million configurations, it will require the same amount of knowledge and be more complex to configure than writing a code, and the project will collapse under it's own weight.