- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201401-33
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: High
    Title: Perl Digest-Base module: Arbitrary code execution
     Date: January 29, 2014
     Bugs: #385487
       ID: 201401-33

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

Synopsis
=======
A vulnerability has been found in the Digest-Base Perl module, allowing
remote attackers to execute arbitrary code.

Background
=========
Digest-Base is a set of Perl modules that calculate message digests

Affected packages
================
    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  perl-core/digest-base       < 1.170.0                 >= 1.170.0 

Description
==========
The vulnerability is caused due to the "Digest->new()" function not
properly sanitising input before using it in an "eval()" call.

Impact
=====
The vulnerability might allow an attacker to execute arbitrary code.

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

Resolution
=========
All Digest-Base module users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=perl-core/digest-base-1.170.0"

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

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

 https://security.gentoo.org/glsa/201401-33

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-201401-33: Perl Digest-Base module: Arbitrary code execution

A vulnerability has been found in the Digest-Base Perl module, allowing remote attackers to execute arbitrary code.

Summary

The vulnerability is caused due to the "Digest->new()" function not properly sanitising input before using it in an "eval()" call.

Resolution

All Digest-Base module users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=perl-core/digest-base-1.170.0"

References

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

Availability

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

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: High
Title: Perl Digest-Base module: Arbitrary code execution
Date: January 29, 2014
Bugs: #385487
ID: 201401-33

Synopsis

A vulnerability has been found in the Digest-Base Perl module, allowing remote attackers to execute arbitrary code.

Background

Digest-Base is a set of Perl modules that calculate message digests

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 perl-core/digest-base < 1.170.0 >= 1.170.0

Impact

===== The vulnerability might allow an attacker to execute arbitrary code.

Workaround

There is no known workaround at this time.

Related News