Fedora has issued an advisory today (August 29): https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/thread/UHKVXMAXF3XW35RVEFHCUR45GWXKGDXO/ The issue comes from an assertion that is reachable and is fixed in 9.11.35.
guillomovitch is both the registered & active maintainer of bind, so assigning this update to you.
Assignee: bugsquad => guillomovitch
Debian has issued an advisory on October 28: https://www.debian.org/security/2021/dsa-4994 Upstream advisory from October 27: https://kb.isc.org/docs/cve-2021-25219 The issue is fixed upstream in 9.11.36.
Status comment: (none) => Fixed upstream in 9.11.36Severity: normal => majorSummary: bind new security issue fixed upstream in 9.11.35 => bind new security issue fixed upstream in 9.11.35 and CVE-2021-25219
Ubuntu has issued an advisory for the new issue on October 28: https://ubuntu.com/security/notices/USN-5126-2
Fedora has issued an advisory for the new issue on November 3: https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/thread/YTKC4E3HUOLYN5IA4EBL4VAQSWG2ZVTX/
Updated package uploaded by Nicolas (subrel should have been removed, but oh well). bind-9.11.36-1.1.mga8 libdns_pkcs11_1115-9.11.36-1.1.mga8 libdns1115-9.11.36-1.1.mga8 bind-devel-9.11.36-1.1.mga8 bind-sdb-9.11.36-1.1.mga8 bind-pkcs11-9.11.36-1.1.mga8 bind-utils-9.11.36-1.1.mga8 bind-pkcs11-utils-9.11.36-1.1.mga8 libisc_pkcs11_1107-9.11.36-1.1.mga8 libisc1107-9.11.36-1.1.mga8 python3-bind-9.11.36-1.1.mga8 bind-dnssec-utils-9.11.36-1.1.mga8 libisccfg163-9.11.36-1.1.mga8 libbind9_161-9.11.36-1.1.mga8 liblwres161-9.11.36-1.1.mga8 libisccc161-9.11.36-1.1.mga8 libirs161-9.11.36-1.1.mga8 bind-pkcs11-devel-9.11.36-1.1.mga8 bind-chroot-9.11.36-1.1.mga8 bind-sdb-chroot-9.11.36-1.1.mga8 from bind-9.11.36-1.1.mga8.src.rpm
Status comment: Fixed upstream in 9.11.36 => (none)Assignee: guillomovitch => qa-bugsCC: (none) => mageia
MGA7-64 Plasma on Lenovo B50 No installation issues. Worked OK as client to my own DNS-server on my desktop machine, and made sure the network setting point to my own dns. Used webmin to define a small DNS-server, then copied the files from /var/lib/named/etc to /etc, restarted named and then got answer from my own dnsusing nslookup. OK for me.
Whiteboard: (none) => MGA8-64-OKCC: (none) => herman.viaene
Validating.
Keywords: (none) => validated_updateCC: (none) => andrewsfarm, sysadmin-bugs
Keywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGASA-2021-0560.html
Status: NEW => RESOLVEDResolution: (none) => FIXED