Bug#991370: libmatio: CVE-2020-36428

Salvatore Bonaccorso carnil at debian.org
Wed Mar 30 19:59:31 BST 2022


Control: reopen -1

Hi Sebastien

Whee does this information come from that this issue is fixed in
1.5.22 upstream?

The OSV-2020-799.yaml cannot be taken into account because it was
marked as such as consequence of
https://github.com/google/oss-fuzz-vulns/issues/12 as far i can see.
Actually it looks that tbeu considers it invalid issue? If this turned
not to be true, what is the fix?

I'm reopening the issue for now to be on safe side.

Regards,
Salvatore



More information about the debian-science-maintainers mailing list