- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 202008-22
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: targetcli-fb: Multiple vulnerabilities
     Date: August 30, 2020
     Bugs: #736086
       ID: 202008-22

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

Synopsis
=======
Multiple vulnerabilities have been found in targetcli-fb, the worst of
which could result in privilege escalation.

Background
=========
Tool for managing the Linux LIO kernel target.

Affected packages
================
    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  sys-block/targetcli-fb       < 2.1.53                  >= 2.1.53

Description
==========
Multiple vulnerabilities have been discovered in targetcli-fb. 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 targetcli-fb users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=sys-block/targetcli-fb-2.1.53"

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

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

 https://security.gentoo.org/glsa/202008-22

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 2020 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-202008-22: targetcli-fb: Multiple vulnerabilities

Multiple vulnerabilities have been found in targetcli-fb, the worst of which could result in privilege escalation.

Summary

Multiple vulnerabilities have been discovered in targetcli-fb. Please review the CVE identifiers referenced below for details.

Resolution

All targetcli-fb users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=sys-block/targetcli-fb-2.1.53"

References


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

Availability

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

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: Normal
Title: targetcli-fb: Multiple vulnerabilities
Date: August 30, 2020
Bugs: #736086
ID: 202008-22

Synopsis

Multiple vulnerabilities have been found in targetcli-fb, the worst of which could result in privilege escalation.

Background

Tool for managing the Linux LIO kernel target.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 sys-block/targetcli-fb < 2.1.53 >= 2.1.53

Impact

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

Workaround

There is no known workaround at this time.

Related News