- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201402-12
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: PAM S/Key: Information disclosure
     Date: February 09, 2014
     Bugs: #482588
       ID: 201402-12

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

Synopsis
=======
PAM S/Key does not clear provided credentials from memory, allowing
local attackers to gain access to cleartext credentials.

Background
=========
PAM S/Key is a pluggable authentication module for the OpenBSD
Single-key Password system.

Affected packages
================
    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  sys-auth/pam_skey           < 1.1.5-r5               >= 1.1.5-r5

Description
==========
Ulrich Müller reported that a Gentoo patch to PAM S/Key does not remove
credentials provided by the user from memory.

Impact
=====
A local attacker with privileged access could inspect a memory dump to
gain access to cleartext credentials provided by users.

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

Resolution
=========
All PAM S/Key users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=sys-auth/pam_skey-1.1.5-r5"

References
=========
[ 1 ] CVE-2013-4285
      http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-4285

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

 https://security.gentoo.org/glsa/201402-12

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 2014 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-201402-12: PAM S/Key: Information disclosure

PAM S/Key does not clear provided credentials from memory, allowing local attackers to gain access to cleartext credentials.

Summary

Ulrich Müller reported that a Gentoo patch to PAM S/Key does not remove credentials provided by the user from memory.

Resolution

All PAM S/Key users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=sys-auth/pam_skey-1.1.5-r5"

References

[ 1 ] CVE-2013-4285 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-4285

Availability

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

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: PAM S/Key: Information disclosure
Date: February 09, 2014
Bugs: #482588
ID: 201402-12

Synopsis

PAM S/Key does not clear provided credentials from memory, allowing local attackers to gain access to cleartext credentials.

Background

PAM S/Key is a pluggable authentication module for the OpenBSD Single-key Password system.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 sys-auth/pam_skey < 1.1.5-r5 >= 1.1.5-r5

Impact

===== A local attacker with privileged access could inspect a memory dump to gain access to cleartext credentials provided by users.

Workaround

There is no known workaround at this time.

Related News