bugtraq - [SECURITY] [DSA 4044-1] swauth security update

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Date: Tue, 21 Nov 2017 16:59:07 +0100
From: Yves-Alexis Perez <corsac@...ian.org>
To: bugtraq@...urityfocus.com
Subject: [SECURITY] [DSA 4044-1] swauth security update

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

- -------------------------------------------------------------------------
Debian Security Advisory DSA-4044-1                   security@...ian.org
https://www.debian.org/security/                        Yves-Alexis Perez
November 21, 2017                     https://www.debian.org/security/faq
- -------------------------------------------------------------------------

Package        : swauth
CVE ID         : CVE-2017-16613
Debian Bug     : 882314

A vulnerability has been discovered in swauth, an authentication system for
Swift, a distributed virtual object store used in Openstack.

The authentication token for an user is saved in clear text to the log file,
which could enable an attacker with access to the logs to bypass the
authentication provided by swauth.

For the stable distribution (stretch), this problem has been fixed in
version 1.2.0-2+deb9u1.

We recommend that you upgrade your swauth packages.

For the detailed security status of swauth please refer to
its security tracker page at:
https://security-tracker.debian.org/tracker/swauth

Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://www.debian.org/security/

Mailing list: debian-security-announce@...ts.debian.org
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAloUSQoACgkQ3rYcyPpX
RFutNAf/aMZwvT4w6JFji9JIMFrmhyFVqcoRy7F4lTkW3X+87RDUgDUEJafzYg88
FGoVX78jVAFIM9f0tRAtlJjHBpclX8nGxsG8OYYf5Gruaz5bpR9HD6ZOf0YIAFnq
k7afT4WAx1qg41KH5IVNDMGvYF434Emf9AnYga7VlI+PURMrqczHeuNsLBzgP/RF
TeLVgN4AF7Vx4lygT1cL8ypWjeow0mkSstDzafjfB0pKF+ZTivfxmf6Xf1000WHn
gbGHveZvTCUfeSIZBd2zL+S7j/GtkyN6q09tO2MwqTQxtFy/oXm2AaaVRLVSJzlC
imWRg0pOOJc5rt02ofjveM+EFc1lGg==
=Td0m
-----END PGP SIGNATURE-----