Advisories ยป MGASA-2020-0375

Updated pdns packages fix security vulnerability

Publication date: 27 Sep 2020
Type: security
Affected Mageia releases : 7
CVE: CVE-2019-10162 , CVE-2019-10163 , CVE-2019-10203 , CVE-2020-17482

Description

An issue has been found in PowerDNS Authoritative Server allowing an
authorized user to cause the server to exit by inserting a crafted record in a
MASTER type zone under their control. The issue is due to the fact that the
Authoritative Server will exit when it runs into a parsing error while looking
up the NS/A/AAAA records it is about to use for an outgoing notify
(CVE-2019-10162).

An issue has been found in PowerDNS Authoritative Server allowing a remote,
authorized master server to cause a high CPU load or even prevent any further
updates to any slave zone by sending a large number of NOTIFY messages. Note
that only servers configured as slaves are affected by this issue
(CVE-2019-10163).

An issue has been found in PowerDNS Authoritative Server allowing an
authorized user to cause the server to exit by inserting a crafted record in a
MASTER type zone under their control. The issue is due to the fact that the
Authoritative Server will exit when it tries to store the notified serial in
the PostgreSQL database, if this serial cannot be represented in 31 bits
(CVE-2019-10203).

An issue has been found in PowerDNS Authoritative Server before 4.3.1 where an
authorized user with the ability to insert crafted records into a zone might be
able to leak the content of uninitialized memory. Such a user could be a
customer inserting data via a control panel, or somebody with access to the
REST API. Crafted records cannot be inserted via AXFR (CVE-2020-17482).

The pdns package has been updated to version 4.1.14, fixing these issues and
several other bugs.  See the upstream changelog for details.

Also note that manual intervention is required to fix the CVE-2019-10203 issue
for those using PostgreSQL with pdns.  See the upstream blog post for details.

References

SRPMS

7/core