Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.security > #5577 > unrolled thread
| Started by | Markus Wollny <markus.wollny@gmail.com> |
|---|---|
| First post | 2019-05-09 09:40 +0200 |
| Last post | 2019-05-12 22:30 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.security
bind9: CVE-2018-5743 Markus Wollny <markus.wollny@gmail.com> - 2019-05-09 09:40 +0200
Re: bind9: CVE-2018-5743 Henrique de Moraes Holschuh <hmh@debian.org> - 2019-05-12 22:30 +0200
| From | Markus Wollny <markus.wollny@gmail.com> |
|---|---|
| Date | 2019-05-09 09:40 +0200 |
| Subject | bind9: CVE-2018-5743 |
| Message-ID | <xVLOO-3cj-15@gated-at.bofh.it> |
Hello, Is there an ETA on the fix for this bind9 vulnerability to be available for Debian Stretch yet? https://security-tracker.debian.org/tracker/CVE-2018-5743 says that the stable branch is still vulnerable (fixed in buster/sid only), even though the Debian bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927932 is already marked as closed. I admit I am not all too familiar with usual Debian security procedures in such cases, but as the bug is rated with a severity rating of grave and it's now two weeks since the public disclosure, I am starting to feel a little worried. Kind regards Markus
[toc] | [next] | [standalone]
| From | Henrique de Moraes Holschuh <hmh@debian.org> |
|---|---|
| Date | 2019-05-12 22:30 +0200 |
| Message-ID | <xX3gC-1Z1-11@gated-at.bofh.it> |
| In reply to | #5577 |
On Thu, 09 May 2019, Markus Wollny wrote: > Is there an ETA on the fix for this bind9 vulnerability to be > available for Debian Stretch yet? It is already available. > https://security-tracker.debian.org/tracker/CVE-2018-5743 says that > the stable branch is still vulnerable (fixed in buster/sid only), even > though the Debian bug report > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927932 is already > marked as closed. Currently, it lists the issue as fixed in the *security* update archive for stable (stretch-security). This means the fix has been released to stable (the current stable is "stretch"). You get timely security updates through the <stable>-security archive. Packages move from <stable>-security to stable only on stable point releases, which happen every 3-5 months, so that we can generate a new set of install-from-CD/DVD/FLASH images that have up-to-date packages and drain the -security archive, which is not as extensively mirrored as the other archives. Note that the installer will update all packages during the install process and has the security archives enabled by default. -- Henrique Holschuh
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.security
csiph-web