DLA-209{0,5}-1 advisory

4 files changed, 64 insertions, 0 deletions

diff --git a/english/lts/security/2020/dla-2090.data b/english/lts/security/2020/dla-2090.data
new file mode 100644
index 00000000000..93ade44aadf
--- /dev/null
+++ b/english/lts/security/2020/dla-2090.data
@@ -0,0 +1,10 @@
+<define-tag pagetitle>DLA-2090-1 qemu</define-tag>
+<define-tag report_date>2020-02-05</define-tag>
+<define-tag secrefs>CVE-2020-7039 Bug#949085</define-tag>
+<define-tag packages>qemu</define-tag>
+<define-tag isvulnerable>yes</define-tag>
+<define-tag fixed>yes</define-tag>
+<define-tag fixed-section>no</define-tag>
+
+#use wml::debian::security
+
diff --git a/english/lts/security/2020/dla-2090.wml b/english/lts/security/2020/dla-2090.wml
new file mode 100644
index 00000000000..4d0ba07c5d7
--- /dev/null
+++ b/english/lts/security/2020/dla-2090.wml
@@ -0,0 +1,21 @@
+<define-tag description>LTS security update</define-tag>
+<define-tag moreinfo>
+
+<p>tcp_emu in tcp_subr.c in libslirp 4.1.0, as used in QEMU 4.2.0, mismanages
+memory, as demonstrated by IRC DCC commands in EMU_IRC.
+This can cause a heap-based buffer overflow or other out-of-bounds access
+which can lead to a DoS or potential execute arbitrary code.</p>
+
+<p>For Debian 8 <q>Jessie</q>, this problem has been fixed in version
+1:2.1+dfsg-12+deb8u13.</p>
+
+<p>We recommend that you upgrade your qemu packages.</p>
+
+<p>Further information about Debian LTS security advisories, how to apply
+these updates to your system and frequently asked questions can be
+found at: <a href="https://wiki.debian.org/LTS">https://wiki.debian.org/LTS</a></p>
+</define-tag>
+
+# do not modify the following line
+#include "$(ENGLISHDIR)/lts/security/2020/dla-2090.data"
+# $Id: $
diff --git a/english/lts/security/2020/dla-2095.data b/english/lts/security/2020/dla-2095.data
new file mode 100644
index 00000000000..e37a540159f
--- /dev/null
+++ b/english/lts/security/2020/dla-2095.data
@@ -0,0 +1,10 @@
+<define-tag pagetitle>DLA-2095-1 storebackup</define-tag>
+<define-tag report_date>2020-02-05</define-tag>
+<define-tag secrefs>CVE-2020-7040 Bug#949393</define-tag>
+<define-tag packages>storebackup</define-tag>
+<define-tag isvulnerable>yes</define-tag>
+<define-tag fixed>yes</define-tag>
+<define-tag fixed-section>no</define-tag>
+
+#use wml::debian::security
+
diff --git a/english/lts/security/2020/dla-2095.wml b/english/lts/security/2020/dla-2095.wml
new file mode 100644
index 00000000000..9437fdceeee
--- /dev/null
+++ b/english/lts/security/2020/dla-2095.wml
@@ -0,0 +1,23 @@
+<define-tag description>LTS security update</define-tag>
+<define-tag moreinfo>
+
+<p>storeBackup.pl in storeBackup through 3.5 relies on the /tmp/storeBackup.lock
+pathname, which allows symlink attacks that possibly lead to privilege
+escalation.</p>
+
+<p>Local users can also create a plain file named /tmp/storeBackup.lock to block
+use of storeBackup until an admin manually deletes that file.</p>
+
+<p>For Debian 8 <q>Jessie</q>, this problem has been fixed in version
+3.2.1-1+deb8u1.</p>
+
+<p>We recommend that you upgrade your storebackup packages.</p>
+
+<p>Further information about Debian LTS security advisories, how to apply
+these updates to your system and frequently asked questions can be
+found at: <a href="https://wiki.debian.org/LTS">https://wiki.debian.org/LTS</a></p>
+</define-tag>
+
+# do not modify the following line
+#include "$(ENGLISHDIR)/lts/security/2020/dla-2095.data"
+# $Id: $