| Summary: | bind new security issue CVE-2015-8000 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | Security | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Sec team <security> |
| Severity: | critical | ||
| Priority: | Normal | CC: | davidwhodgins, paul.blackburn, sysadmin-bugs, wilcal.int |
| Version: | 5 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| URL: | http://lwn.net/Vulnerabilities/668124/ | ||
| Whiteboard: | has_procedure MGA5-64-OK advisory | ||
| Source RPM: | bind-9.10.2.P4-1.mga5.src.rpm | CVE: | |
| Status comment: | |||
|
Description
David Walser
2015-12-16 01:14:14 CET
Testing procedure: similar to https://bugs.mageia.org/show_bug.cgi?id=9163#c8 Whiteboard:
(none) =>
has_procedure Debian has issued an advisory for this on December 15: https://www.debian.org/security/2015/dsa-3420 preparing to test x86_64 rpms CC:
(none) =>
paul.blackburn tested OK on x86_64
David Walser
2015-12-16 19:30:38 CET
URL:
(none) =>
http://lwn.net/Vulnerabilities/668124/ (In reply to Paul Blackburn from comment #4) > tested OK on x86_64 Paul could you expand a little, or a lot, on how you tested bind. Thanks CC:
(none) =>
wilcal.int Tested the updated RPMs on a name server with SOA for a domain and several subnets. Verified BIND handled forward and inverse queries for the domain, subnets, and for external queries. Searched for a proof of concept for the vulnerability addressed by this update but was not able to find one. $ dig mageia.org|grep SERVER ;; SERVER: 127.0.0.1#53(127.0.0.1) Confirmed working here. Validating the update. I'll add the advisory to svn shortly, if it isn't already there. Keywords:
(none) =>
validated_update Advisory uploaded to svn. Whiteboard:
has_procedure MGA5-64-OK =>
has_procedure MGA5-64-OK advisory An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGASA-2015-0481.html Status:
NEW =>
RESOLVED This is two bugs in a week that I typoed the CVE in the advisory text, but had the correct CVE in the references and bug title. I have fixed it in SVN. When uploading the advisories, please make sure the CVEs match. If they don't, please ask for clarification if you're not sure which is correct. I apologize for the errors. |