PatchTheCVEfeverwarn firmware vulnerabilities and fixes
Recent CVEs affecting feverwarn firmware, with upgrade or downgrade steps. 6 tracked.
Also searched as: feverwarnfirmware.
feverwarn firmware has 6 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 0. Most recent: 2024-02-01. Highest priority: CVE-2023-49617 (score 54/100).
- CVE-2023-6221 HIGH 7.7 MITIGATE The cloud provider MachineSense uses for integration and deployment for multiple MachineSense devices, such a
- CVE-2023-49617 CRITICAL 10.0 MITIGATE The MachineSense application programmable interface (API) is improperly protected and can be accessed wit
- CVE-2023-49610 HIGH 8.1 MITIGATE MachineSense FeverWarn Raspberry Pi-based devices lack input sanitization, which could allow an att
- CVE-2023-49115 HIGH 7.5 MITIGATE MachineSense devices use unauthenticated MQTT messaging to monitor devices and remote viewing of sensor
- CVE-2023-47867 HIGH 8.8 MITIGATE MachineSense FeverWarn devices are configured as Wi-Fi hosts in a way that attackers within range cou
- CVE-2023-46706 CRITICAL 9.1 MITIGATE Multiple MachineSense devices have credentials unable to be changed by the user or administrator.
FAQ
How do I fix feverwarn firmware vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is feverwarn firmware being exploited right now?
None of the tracked feverwarn firmware CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which feverwarn firmware CVE should I patch first?
CVE-2023-49617 currently ranks highest (54/100): The MachineSense application programmable interface (API) is improperly protected and can be accessed wit.