| Summary: | unbound new security issue CVE-2019-16866 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | Security | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Sec team <security> |
| Severity: | major | ||
| Priority: | Normal | CC: | andrewsfarm, eatdirt, herman.viaene, sysadmin-bugs, tmb |
| Version: | 7 | Keywords: | advisory, validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA7-64-OK | ||
| Source RPM: | unbound-1.9.1-3.mga8.src.rpm | CVE: | |
| Status comment: | Fixed upstream in 1.9.4 | ||
|
Description
David Walser
2019-10-31 04:46:13 CET
David Walser
2019-10-31 04:46:39 CET
Whiteboard:
(none) =>
MGA7TOO Ubuntu has issued an advisory for this on October 8: https://usn.ubuntu.com/4149-1/ Assigning to ChrisD as the 'unbound' registered maintainer. Assignee:
bugsquad =>
eatdirt I have uploaded version 1.9.4 for mga 7 in updates_testing (cauldron also updated). You can test if the unbound service runs fine with (as root): systemctl start unbound systemctl status unbound should return a green "active (running)". Suggested advisory: ======================== Updated unbound package to version 1.9.4 to fix security vulnerabilities. Versions before 1.9.4 allow accesses to uninitialized memory, which would permit remote attackers to trigger a crash (CVE-2019-16866). References: https://www.debian.org/security/2019/dsa-4544 https://security-tracker.debian.org/tracker/CVE-2019-16866 ======================== Updated packages in core/updates_testing: ======================== lib(64)unbound8-1.9.4-1.mga7 lib(64)unbound-devel-1.9.4-1.mga7 unbound-1.9.4-1.mga7 python2-unbound-1.9.4-1.mga7 python3-unbound-1.9.4-1.mga7 Source RPMs: unbound-1.9.4-1.mga7.src.rpm CC:
(none) =>
eatdirt MGA7-64 Plasma on Lenovo B50 No installation issues Ref bug22423 Comment 2 for testing. # systemctl start unbound # systemctl -l status unbound ● unbound.service - Unbound DNS Resolver Loaded: loaded (/usr/lib/systemd/system/unbound.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2019-11-06 10:22:53 CET; 3s ago Main PID: 26930 (unbound) Memory: 5.6M CGroup: /system.slice/unbound.service └─26930 /usr/sbin/unbound -c /etc/unbound/unbound.conf nov 06 10:22:53 mach5.hviaene.thuis systemd[1]: Started Unbound DNS Resolver. nov 06 10:22:53 mach5.hviaene.thuis unbound[26930]: [26930:0] notice: init module 0: validator nov 06 10:22:53 mach5.hviaene.thuis unbound[26930]: [26930:0] notice: init module 1: iterator nov 06 10:22:53 mach5.hviaene.thuis unbound[26930]: [26930:0] info: start of service (unbound 1.9.4). OK then. Whiteboard:
MGA7TOO =>
MGA7TOO MGA7-64-OK
Thomas Backlund
2019-11-06 22:51:02 CET
Version:
Cauldron =>
7 Validating. Advisory in Comment 3. Keywords:
(none) =>
validated_update
Thomas Backlund
2019-11-07 22:20:32 CET
Keywords:
(none) =>
advisory An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGASA-2019-0317.html Resolution:
(none) =>
FIXED |