Closed pyryk closed 2 years ago
Thanks!
This vulnerability is not directly exploitable, since RuuviCollector doesn't log any totally uncontrolled input. The closest to that is logging some of the received raw data from hcidump (in hex bytes) in case an uncaught exception is thrown, although a theoretical attack vector exists if someone manages to get hcidump to output something else. Either way it's good to fix this, but it's not a critical issue in this case
Ah, thanks for the clarification. But agree it's good to fix just in case (and to guard against some potential future usage)
This PR updates the log4j dependency in order to address CVE-2021-44228.
As far as I understand, exploiting the vulnerability would require physical proximity. Therefore, the vulnerability is not as critical as in many other pieces of software, but it might make sense to address this just to be on the safe side.