1 files changed, 69 insertions, 0 deletions
diff --git a/metadata/glsa/glsa-201206-01.xml b/metadata/glsa/glsa-201206-01.xml
new file mode 100644
index 000000000000..39b724be14d7
--- /dev/null
+++ b/metadata/glsa/glsa-201206-01.xml
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
+<glsa id="201206-01">
+  <title>BIND: Multiple vulnerabilities</title>
+  <synopsis>Multiple vulnerabilities have been found in BIND, the worst of
+    which allowing to cause remote Denial of Service.
+  </synopsis>
+  <product type="ebuild">bind</product>
+  <announced>2012-06-02</announced>
+  <revised count="1">2012-06-02</revised>
+  <bug>347621</bug>
+  <bug>356223</bug>
+  <bug>368863</bug>
+  <bug>374201</bug>
+  <bug>374623</bug>
+  <bug>390753</bug>
+  <access>remote</access>
+  <affected>
+    <package name="net-dns/bind" auto="yes" arch="*">
+      <unaffected range="ge">9.7.4_p1</unaffected>
+      <vulnerable range="lt">9.7.4_p1</vulnerable>
+    </package>
+  </affected>
+  <background>
+    <p>BIND is the Berkeley Internet Name Domain Server.</p>
+  </background>
+  <description>
+    <p>Multiple vulnerabilities have been discovered in BIND. Please review the
+      CVE identifiers referenced below for details.
+    </p>
+  </description>
+  <impact type="normal">
+    <p>The vulnerabilities allow remote attackers to cause a Denial of Service
+      (daemon crash) via a DNS query, to bypass intended access restrictions,
+      to incorrectly cache a ncache entry and a rrsig for the same type and to
+      incorrectly mark zone data as insecure.
+    </p>
+  </impact>
+  <workaround>
+    <p>There is no known workaround at this time.</p>
+  </workaround>
+  <resolution>
+    <p>All bind users should upgrade to the latest version:</p>
+    
+    <code>
+      # emerge --sync
+      # emerge --ask --oneshot --verbose "&gt;=net-dns/bind-9.7.4_p1"
+    </code>
+    
+    <p>NOTE: This is a legacy GLSA. Updates for all affected architectures are
+      available since December 22, 2011. It is likely that your system is
+      already
+      no longer affected by this issue. 
+    </p>
+  </resolution>
+  <references>
+    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3613">CVE-2010-3613</uri>
+    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3614">CVE-2010-3614</uri>
+    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3615">CVE-2010-3615</uri>
+    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3762">CVE-2010-3762</uri>
+    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-0414">CVE-2011-0414</uri>
+    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-1910">CVE-2011-1910</uri>
+    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-2464">CVE-2011-2464</uri>
+    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-2465">CVE-2011-2465</uri>
+    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-4313">CVE-2011-4313</uri>
+  </references>
+  <metadata timestamp="2011-10-07T23:37:02Z" tag="requester">craig</metadata>
+  <metadata timestamp="2012-06-02T13:53:49Z" tag="submitter">craig</metadata>
+</glsa>