View | Details | Raw Unified | Return to bug 250318 | Differences between
and this patch

Collapse All | Expand All

(-)vuln.xml (+32 lines)
Lines 58-63 Link Here
58
  * Do not forget port variants (linux-f10-libxml2, libxml2, etc.)
58
  * Do not forget port variants (linux-f10-libxml2, libxml2, etc.)
59
-->
59
-->
60
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">
60
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">
61
  <vuln vid="a6860b11-0dee-11eb-94ff-6805ca2fa271">
62
    <topic>powerdns-recursor -- cache pollution</topic>
63
    <affects>
64
      <package>
65
	<name>powerdns-recursor</name>
66
	<range><ge>4.3.0</ge><lt>4.3.4</lt></range>
67
	<range><ge>4.2.0</ge><lt>4.2.4</lt></range>
68
	<range><ge>4.1.0</ge><lt>4.1.17</lt></range>
69
      </package>
70
    </affects>
71
    <description>
72
      <body xmlns="http://www.w3.org/1999/xhtml">
73
	<p>PowerDNS Team reports:</p>
74
	<blockquote cite="https://doc.powerdns.com/recursor/changelog/4.3.html#change-4.3.5">
75
	  <p>CVE-2020-25829: An issue has been found in PowerDNS Recursor where a remote attacker can cause the
76
	   cached records for a given name to be updated to the ‘Bogus’ DNSSEC validation state, instead of
77
	   their actual DNSSEC ‘Secure’ state, via a DNS ANY query. This results in a denial of service for
78
	   installations that always validate (dnssec=validate) and for clients requesting validation when
79
	   on-demand validation is enabled (dnssec=process).</p>
80
	</blockquote>
81
      </body>
82
    </description>
83
    <references>
84
      <url>https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2020-07.html</url>
85
      <cvename>CVE-2020-25829</cvename>
86
    </references>
87
    <dates>
88
      <discovery>2020-10-13</discovery>
89
      <entry>2020-10-14</entry>
90
    </dates>
91
  </vuln>
92
61
  <vuln vid="42926d7b-0da3-11eb-8dbd-6451062f0f7a">
93
  <vuln vid="42926d7b-0da3-11eb-8dbd-6451062f0f7a">
62
    <topic>Flash Player -- arbitrary code execution</topic>
94
    <topic>Flash Player -- arbitrary code execution</topic>
63
    <affects>
95
    <affects>

Return to bug 250318