STM32CubeMonitor Security/Credentials critical issues
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-03-23 5:17 AM
Hi everyone.
I'm trying to secure STM32CubeMonitor Editor and UI as defined to Node-RED, but is not possible secure STM32CubeMonitor.
After define a user and password at settings.js (even only for STM32 CubeMonitor) the editor and UI breaks and are simply useless.
This is a critical issue nowadays, not been able to secure a webserver that can be exposed to remote access, to provide REST API's and so on...
Tested STM32CubeMonitor v1.3.0
In other hand, this features works perfectly on native Node-RED instances.
There is a known workaround to secure STM32CubeMonitor editor and UI with user-password login?
Solved! Go to Solution.
- Labels:
-
STM32CubeMonitor
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-10-31 9:46 AM
Hi @Andrea cavani​
The release 1.5.0 is online. It should be possible now to secure the editor properly.
Please, let us know if it is ok with the new version.
Please note: In the default setting.js, the remote access is now disabled by default.
Best regards
Stephane
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-03-24 2:16 AM
Hello everyone.
There are some possibility of getting an answer from STMicroelectronics people?
Anyone has facing this issue or have this need?
Thanks for your time and attention
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-03-30 3:45 AM
Hello to everyone.
Does anyone know a wrokaround to this critical issue?
Thanks for your attention.
Best regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-03-31 12:34 AM
Hello @_acv_atr​
I tried using user and password at settings.js for both STM32CubeMonitor-1.3.0 and newly published 1.4.0 and didn't face any issue such as the one you mentioned (see attached settings.js). Can you detail your environment and the modification you made.
// Securing Node-RED
// -----------------
// To password protect the Node-RED editor and admin API, the following
// property can be used. See http://nodered.org/docs/security.html for details.
adminAuth: {
type: "credentials",
users: [{
username: "admin",
password: "$2a$08$zZWtXTja0fB1pzD4sHCMyOCMYz2Z6dNbM6tl8sJogENOMcxWV9DN.",
permissions: "*"
}],
default: {
permissions: "read"
}
},
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-03-31 4:24 AM
Hello @Richard.Chvr​
Going in more detail:
OP: Ubuntu 20.04 desktop
CubeMonitor: v1.3.0
user: admin
password: admin_1234#
FLow: default from ST, after fresh installation
Editor asking for password as expected:
Editor stuck after enter correct password:
Node-RED UI not working properly after correct login
Please consider flow and settings on attachment.
If you need further details, let me know.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-03-31 6:18 AM
@_acv_atr​
Thank for these details, I've tested this configuration on my ubuntu machine (I previously successfully tested it on windows) and I confirm the issue you face. Will investigate and come back to you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-05-02 2:49 AM
@Richard.Chvr​
Any news or update about this subject?
Thanks for your support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-05-09 7:00 AM
Hello @Richard.Chvr​ .
There is any update or workaround regarding this critical issue?
Thank your for your attention
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-05-09 8:23 AM
Hi @Community member​
Problem have been submitted to dev team. Still waiting for feedback .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-09-29 9:03 AM
Hi @Andrea cavani​
Issue should be corrected in next release 1.5.0 that will come soon.
