Source: libmatio
Source-Version: 1.5.22-1
Hi Sébastien,
Thanks a lot for the quick followups!
On Wed, Mar 30, 2022 at 09:14:06PM +0200, Sébastien Villemot wrote:
> Le mercredi 30 mars 2022 à 21:08 +0200, Sébastien Villemot a écrit :
> > > The OSV-2020-799.yaml cannot be taken into account becaus
Le mercredi 30 mars 2022 à 21:08 +0200, Sébastien Villemot a écrit :
> > 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 inval
Hi Salvatore,
Le mercredi 30 mars 2022 à 20:59 +0200, Salvatore Bonaccorso a écrit :
> Whee does this information come from that this issue is fixed in
> 1.5.22 upstream?
It’s what upstream changelog for 1.5.22 says:
https://salsa.debian.org/science-team/libmatio/-/blob/master/NEWS#L6
> The OSV-
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 lo
Source: libmatio
Version: 1.5.19-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for libmatio.
CVE-2020-36428[0]:
| matio (aka MAT File I/O Library) 1.5.18 through 1.5.21 has a heap-
| based buffer
5 matches
Mail list logo