- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201203-04
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: libxml2: Denial of Service
     Date: March 06, 2012
     Bugs: #405261
       ID: 201203-04

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

Synopsis
=======
A hash collision vulnerability in libxml2 allows remote attackers to
cause a Denial of Service condition.

Background
=========
libxml2 is the XML C parser and toolkit developed for the Gnome
project.

Affected packages
================
    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  dev-libs/libxml2            < 2.7.8-r5               >= 2.7.8-r5

Description
==========
libxml2 does not properly randomize hash functions to protect against
hash collision attacks.

Impact
=====
A remote attacker could entice a user or automated system to open a
specially crafted XML document with an application using libxml2
resulting in a Denial of Service condition.

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

Resolution
=========
All libxml2 users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=dev-libs/libxml2-2.7.8-r5"

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

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

 https://security.gentoo.org/glsa/201203-04

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 2012 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-201203-04: libxml2: Denial of Service

A hash collision vulnerability in libxml2 allows remote attackers to cause a Denial of Service condition.

Summary

libxml2 does not properly randomize hash functions to protect against hash collision attacks.

Resolution

All libxml2 users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=dev-libs/libxml2-2.7.8-r5"

References

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

Availability

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

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: libxml2: Denial of Service
Date: March 06, 2012
Bugs: #405261
ID: 201203-04

Synopsis

A hash collision vulnerability in libxml2 allows remote attackers to cause a Denial of Service condition.

Background

libxml2 is the XML C parser and toolkit developed for the Gnome project.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-libs/libxml2 < 2.7.8-r5 >= 2.7.8-r5

Impact

===== A remote attacker could entice a user or automated system to open a specially crafted XML document with an application using libxml2 resulting in a Denial of Service condition.

Workaround

There is no known workaround at this time.

Related News