- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 202101-34
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Low
    Title: Telegram Desktop: Multiple vulnerabilities
     Date: January 27, 2021
     Bugs: #736774, #749288
       ID: 202101-34

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
=======
Multiple vulnerabilities have been found in Telegram, the worst of
which could result in information disclosure.

Background
=========
Telegram is a messaging app with a focus on speed and security.

Affected packages
================
    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  net-im/telegram-desktop      < 2.4.4                    >= 2.4.4

Description
==========
Multiple vulnerabilities have been discovered in Telegram Desktop.
Please review the CVE identifiers referenced below for details.

Impact
=====
Please review the referenced CVE identifiers for details.

Workaround
=========
There is no known workaround at this time.

Resolution
=========
All Telegram Desktop users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=net-im/telegram-desktop-2.4.4"

References
=========
[ 1 ] CVE-2020-17448
      https://nvd.nist.gov/vuln/detail/CVE-2020-17448
[ 2 ] CVE-2020-25824
      https://nvd.nist.gov/vuln/detail/CVE-2020-25824

Availability
===========
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202101-34

Concerns?
========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
======
Copyright 2021 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5/

Gentoo: GLSA-202101-34: Telegram Desktop: Multiple vulnerabilities

Multiple vulnerabilities have been found in Telegram, the worst of which could result in information disclosure.

Summary

Multiple vulnerabilities have been discovered in Telegram Desktop. Please review the CVE identifiers referenced below for details.

Resolution

All Telegram Desktop users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=net-im/telegram-desktop-2.4.4"

References

[ 1 ] CVE-2020-17448 https://nvd.nist.gov/vuln/detail/CVE-2020-17448 [ 2 ] CVE-2020-25824 https://nvd.nist.gov/vuln/detail/CVE-2020-25824

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202101-34

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity
Severity: Low
Title: Telegram Desktop: Multiple vulnerabilities
Date: January 27, 2021
Bugs: #736774, #749288
ID: 202101-34

Synopsis

Multiple vulnerabilities have been found in Telegram, the worst of which could result in information disclosure.

Background

Telegram is a messaging app with a focus on speed and security.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 net-im/telegram-desktop < 2.4.4 >= 2.4.4

Impact

===== Please review the referenced CVE identifiers for details.

Workaround

There is no known workaround at this time.

Related News