regen v9_9

diff --git a/doc/arm/Bv9ARM.ch09.html b/doc/arm/Bv9ARM.ch09.html
index 60f80b99c577bc20407dbff7985f283f36e1288f..b3fa7a76c64db691b506fbfd006c4ed6afa99afc 100644 (file)
--- a/doc/arm/Bv9ARM.ch09.html
+++ b/doc/arm/Bv9ARM.ch09.html
@@ -83,30 +83,30 @@
 <a name="relnotes_security"></a>Security Fixes</h3></div></div></div>
 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
 <li class="listitem"><p>
-         Insufficient testing when parsing a message allowed
-         records with an incorrect class to be be accepted,
-         triggering a REQUIRE failure when those records
-         were subsequently cached.  This flaw is disclosed
-         in CVE-2015-8000. [RT #40987]
+         The resolver could abort with an assertion failure due to
+         improper DNAME handling when parsing fetch reply
+         messages. This flaw is disclosed in CVE-2016-1286. [RT #41753]
        </p></li>
 <li class="listitem"><p>
-         Incorrect reference counting could result in an INSIST
-         failure if a socket error occurred while performing a
-         lookup.  This flaw is disclosed in CVE-2015-8461. [RT#40945]
+         Malformed control messages can trigger assertions in named
+         and rndc. This flaw is disclosed in CVE-2016-1285. [RT
+         #41666]
        </p></li>
 <li class="listitem"><p>
          Specific APL data could trigger an INSIST.  This flaw
          is disclosed in CVE-2015-8704. [RT #41396]
        </p></li>
 <li class="listitem"><p>
-         Malformed control messages can trigger assertions in named
-         and rndc. This flaw is disclosed in CVE-2016-1285. [RT
-         #41666]
+         Incorrect reference counting could result in an INSIST
+         failure if a socket error occurred while performing a
+         lookup.  This flaw is disclosed in CVE-2015-8461. [RT#40945]
        </p></li>
 <li class="listitem"><p>
-         The resolver could abort with an assertion failure due to
-         improper DNAME handling when parsing fetch reply
-         messages. This flaw is disclosed in CVE-2016-1286. [RT #41753]
+         Insufficient testing when parsing a message allowed
+         records with an incorrect class to be be accepted,
+         triggering a REQUIRE failure when those records
+         were subsequently cached.  This flaw is disclosed
+         in CVE-2015-8000. [RT #40987]
        </p></li>
 </ul></div>
 </div>

diff --git a/doc/arm/notes.html b/doc/arm/notes.html
index 5f637640b48e45e26da21e8a1668aa6e5179a4c2..8756f118bc17562eb810ad74b5d3d460a8b3f305 100644 (file)
--- a/doc/arm/notes.html
+++ b/doc/arm/notes.html
@@ -45,30 +45,30 @@
 <a name="relnotes_security"></a>Security Fixes</h3></div></div></div>
 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
 <li class="listitem"><p>
-         Insufficient testing when parsing a message allowed
-         records with an incorrect class to be be accepted,
-         triggering a REQUIRE failure when those records
-         were subsequently cached.  This flaw is disclosed
-         in CVE-2015-8000. [RT #40987]
+         The resolver could abort with an assertion failure due to
+         improper DNAME handling when parsing fetch reply
+         messages. This flaw is disclosed in CVE-2016-1286. [RT #41753]
        </p></li>
 <li class="listitem"><p>
-         Incorrect reference counting could result in an INSIST
-         failure if a socket error occurred while performing a
-         lookup.  This flaw is disclosed in CVE-2015-8461. [RT#40945]
+         Malformed control messages can trigger assertions in named
+         and rndc. This flaw is disclosed in CVE-2016-1285. [RT
+         #41666]
        </p></li>
 <li class="listitem"><p>
          Specific APL data could trigger an INSIST.  This flaw
          is disclosed in CVE-2015-8704. [RT #41396]
        </p></li>
 <li class="listitem"><p>
-         Malformed control messages can trigger assertions in named
-         and rndc. This flaw is disclosed in CVE-2016-1285. [RT
-         #41666]
+         Incorrect reference counting could result in an INSIST
+         failure if a socket error occurred while performing a
+         lookup.  This flaw is disclosed in CVE-2015-8461. [RT#40945]
        </p></li>
 <li class="listitem"><p>
-         The resolver could abort with an assertion failure due to
-         improper DNAME handling when parsing fetch reply
-         messages. This flaw is disclosed in CVE-2016-1286. [RT #41753]
+         Insufficient testing when parsing a message allowed
+         records with an incorrect class to be be accepted,
+         triggering a REQUIRE failure when those records
+         were subsequently cached.  This flaw is disclosed
+         in CVE-2015-8000. [RT #40987]
        </p></li>
 </ul></div>
 </div>