View | Details | Raw Unified | Return to bug 249560 | 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="b371db92-fe34-11ea-b90e-6805ca2fa271">
62
    <topic>powerdns -- Leaking uninitialised memory through crafted zone records</topic>
63
    <affects>
64
      <package>
65
	<name>powerdns</name>
66
	<range><ge>4.3.0</ge><lt>4.3.1</lt></range>
67
	<range><ge>4.2.0</ge><lt>4.2.3</lt></range>
68
	<range><ge>4.1.0</ge><lt>4.1.14</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/authoritative/changelog/4.3.html#change-4.3.1">
75
	  <p>CVE-2020-17482: An issue has been found in PowerDNS Authoritative Server before 4.3.1 where
76
	     an authorized user with the ability to insert crafted records into a zone might be able to
77
	     leak the content of uninitialized memory. Such a user could be a customer inserting data
78
	     via a control panel, or somebody with access to the REST API. Crafted records cannot be
79
	     inserted via AXFR.</p>
80
	</blockquote>
81
      </body>
82
    </description>
83
    <references>
84
      <url>https://doc.powerdns.com/authoritative/security-advisories/powerdns-advisory-2020-05.html</url>
85
      <cvename>CVE-2020-17482</cvename>
86
    </references>
87
    <dates>
88
      <discovery>2020-09-22</discovery>
89
      <entry>2020-09-24</entry>
90
    </dates>
91
  </vuln>
92
61
  <vuln vid="0a305431-bc98-11ea-a051-001b217b3468">
93
  <vuln vid="0a305431-bc98-11ea-a051-001b217b3468">
62
    <topic>Gitlab -- Multiple Vulnerabilities</topic>
94
    <topic>Gitlab -- Multiple Vulnerabilities</topic>
63
    <affects>
95
    <affects>

Return to bug 249560