Closed Zero0one1 closed 3 years ago
Seeing as both errors seems to be ignored, can we just set the 5th param to NULL? If so, I'd love a pull request with that fix please.
Agree. I think setting to NULL should work : )
CVE-2021-42523 was assigned to this issue.
Eigh? Can you explain how a memory leak is a Information Disclosure? That's completely wrong. This should not be a CVE.
According to libsqlite3 API document, "To avoid memory leaks, the application should invoke sqlite3_free() on error message strings returned through the 5th parameter of sqlite3_exec() after the error message string is no longer needed."
https://github.com/hughsie/colord/blob/1572d92bb69de7632841bf17f3cb81534881c3c6/src/cd-device-db.c#L93-L103