Tonight I got a report about a crash inside the serial connector’s communication loop. While this seems to be a quite rare problem, given that we are currently already looking at over 2200 instances updated to 2.0.0 with a collective print time of over 6500h just 48 hours after 2.0.0’s release, I still decided to consider this a high priority issue given it’s blocking nature. So, here you have 2.0.1, with a fix for this and two fixes for slightly less pressing issues I had already been preparing:
🔒 Security fixes
Classic Webcam snapshot credentials are returned by /api/settings to users without the SETTINGS permission, severity Low (2.1): OctoPrint versions from 1.11.0 up until version 2.0.0 contain an invalid permission restriction on the bundled Classic Webcam Plugin’s snapshot credentials, allowing users with permission
SETTINGS_READto read those, even though they should be restricted to theSETTINGSpermission.See also the GitHub Security Advisory. A CVE has been requested from GitHub but not yet been provided.
🐛 Bug fixes
Core
- Redact connection parameters on
/api/connectionwhen the requesting account does not have theCONNECTIONpermission. This is to prevent possible credentials leaking as part of the parameters needed for connectors, e.g. API keys, serial numbers, host names etc.Serial Connector Plugin
- #5486: Fix an error leading to a crash in the communication loop when the firmware did not report a
FIRMWARE_NAME(orNAME) as response toM115.
You can also take a look at the changelog on GitHub.
Like every single release (and release candidate) of OctoPrint ever since early 2016 this release was made possible only through continued financial support by people like you! 💕
Click here if you enjoy OctoPrint and want to help with its funding!
Issues while updating?
On every new OctoPrint release we see some people run into the same issues with outdated or broken environments all over again. If you encounter a problem during update, please check this collection of the most common issues encountered over the past couple of release cycles first, and test if the included fixes solve your problem.
Also make sure to check any of the heads-ups listed below.
Heads-ups
The heads-ups from 2.0.0 still apply, please read them carefully, they might impact you and how you use OctoPrint! Also see the Further Information and Links below for more information, where to find help and how to roll back.
Thanks
Special thanks to everyone who contributed to this release and provided full, analyzable bug reports, suggestions, feedback and - of course - funding !
Also another Thank you! to @rlawltnrj for the responsible disclosure of vulnerabilities fixed in this release.
Further Information
If connected to the internet, OctoPrint will allow you to apply this update automatically via an update notification. It may take up to 24h for this notification to pop up, so don't be alarmed if it doesn't show up immediately after reading this. You can force the update however via Settings > Software Update > Advanced options > Force check for update.
If your update fails chances are high you are running into one of the common update issues listed with fixes here, so please go through that FAQ entry first.
If you have any problems with your OctoPrint installation, please seek support on the community forum.
