On Sat, May 11, 2019 at 05:38:50PM +0300, Коля Гурьев wrote:
> As John Preston said, there was no a special fix of the issue in 1.5.12.
> It is mistake that this version is considered to contain the fix.
> And as far as I can see, Telegram Desktop has no a fix of this CVE yet.
Ack, ok.
Cheers,
Hi,
09.05.2019 23:42, Moritz Mühlenhoff пишет:
> What's the status? Has upstream been contacted for an isolated fix, are
> you planning to address this for buster?
As John Preston said, there was no a special fix of the issue in 1.5.12.
It is mistake that this version is considered to contain th
On Sun, Apr 21, 2019 at 10:18:12PM +0200, Moritz Muehlenhoff wrote:
> Package: telegram-desktop
> Severity: grave
> Tags: security
>
> This was assigned CVE-2019-10044 and is claimed to be fixed in 1.5.12:
> https://github.com/blazeinfosec/advisories/blob/master/telegram-advisory.txt
What's the s
Package: telegram-desktop
Severity: grave
Tags: security
This was assigned CVE-2019-10044 and is claimed to be fixed in 1.5.12:
https://github.com/blazeinfosec/advisories/blob/master/telegram-advisory.txt
Cheers,
Moritz
4 matches
Mail list logo