Skip to main content
User16782158065171037550
User16782158065171037550
Associate II
April 28, 2020
Question

Security Issue - installation on Ubuntu changes the owner:group of /etc

  • April 28, 2020
  • 6 replies
  • 2085 views

We have a issue installing en.st-stm32cubeide_1.3.0_5720_20200220_1053_amd64.sh on ubuntu, the installation changes the ower:group from root:root to 43655:43655

Reproducible: yes

OS: Ubuntu 18.04 & ubuntu 20.04

ST software: en.st-stm32cubeide_1.3.0_5720_20200220_1053_amd64.sh.zip

Please refer attached files.

lsla.txt - directory listing of / before installation

lsla_after_install.txt - directory listing after installation

notice the change in the . & .. and /etc diectory

ufw.txt - ufw firewall status

Please look into it and we need a fix for this issue.

Regards,

Milind

This topic has been closed for replies.

6 replies

Markus GIRDLAND
Markus GIRDLAND
ST Employee
April 28, 2020

I'll try to get a hold of an Ubuntu to give it a try and if I'm able to reproduce as well I'll write a ticket.

Markus GIRDLAND
Markus GIRDLAND
ST Employee
April 28, 2020

It could be reproduced so I'll write a ticket. Thank you for raising the issue!

User16782158065171037550
User16782158065171037550Author
Associate II
April 28, 2020

Thanks for the quick reply, look forward to get a solution at the earliest.

Markus GIRDLAND
Markus GIRDLAND
ST Employee
May 12, 2020

We just released an updated version of the Linux installer (still version 1.3.0) that has fixed this issue, so if you download the latest available installer this issue should now be fixed.

User16782158065171037550
User16782158065171037550Author
Associate II
May 14, 2020

Installed the patched version on Ubuntu 20.04, issue fixed.:grinning_face:

Fase.1
Fase.1
Visitor II
April 7, 2021

I was able to solve this trouble. Apparently STMCube appears for java on its own (does now not use the entry designated iny PATH) as you can see. I had an old version of java that I changed into now not privy to in application files (x86). I actually rename the directory and now all is well. I determined this solution in:

Terms & ConditionsAccessibility statement