[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#705468: marked as done (libytnef: Buffer overflow (CVE-2010-5109))

Your message dated Thu, 10 Oct 2013 12:48:28 +0000
with message-id <E1VUFfI-000101-86@franck.debian.org>
and subject line Bug#705468: fixed in libytnef 1.5-5
has caused the Debian Bug report #705468,
regarding libytnef: Buffer overflow (CVE-2010-5109)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
705468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705468
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libytnef
Version: 1.5-4
Severity: normal
Tags: security

Upstream bug: http://sourceforge.net/p/ytnef/bugs/13/
Red Hat bug: https://bugzilla.redhat.com/show_bug.cgi?id=831322
Red Hat fix: https://bugzilla.redhat.com/attachment.cgi?id=596239&action=diff

---
Henri Salo

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
Source: libytnef
Source-Version: 1.5-5

We believe that the bug you reported is fixed in the latest version of
libytnef, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 705468@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose <doko@debian.org> (supplier of updated libytnef package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Thu, 10 Oct 2013 14:16:21 +0200
Source: libytnef
Binary: libytnef0 libytnef0-dev
Architecture: source amd64
Version: 1.5-5
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Matthias Klose <doko@debian.org>
Description: 
 libytnef0  - improved decoder for application/ms-tnef attachments
 libytnef0-dev - improved decoder for application/ms-tnef attachments
Closes: 705468
Changes: 
 libytnef (1.5-5) unstable; urgency=low
 .
   * QA upload.
   * Use dh_autotools-dev to update config.{sub,guess} for AArch64.
   * Fix heap overflow (CVE-2010-5109). Closes: #705468.
   * Use dpkg-buildflags for the build.
Checksums-Sha1: 
 c40d0ef8fa4a634d43a8975dfec5381a2b52e8e4 1130 libytnef_1.5-5.dsc
 cbe16de5282ecfdaa946173c7d3f819a04e12ead 380636 libytnef_1.5-5.debian.tar.gz
 9bfc8f0dd770d96ba0e7c7b8e3a99ec3ff1208dc 18962 libytnef0_1.5-5_amd64.deb
 a1a01b46c76de31a2a1663fe381ffbc8917f2c81 23634 libytnef0-dev_1.5-5_amd64.deb
Checksums-Sha256: 
 a0c91fc6fab99f67ab9cbc680858a9367ce534d164d334b53b695bcaa3094d6f 1130 libytnef_1.5-5.dsc
 6362328b11e77cc6debc4ebcc406da240f9d7af95e998ee9de3fd5d68d5bed13 380636 libytnef_1.5-5.debian.tar.gz
 b7ef9535ad556a2fca1ff49d0e4b602ec72154e2c3a53e16819cce6621c2e6a4 18962 libytnef0_1.5-5_amd64.deb
 1ddd3591e2669c253b0b078d66ac8c8719812b8de36bbef7286ca22439a568e4 23634 libytnef0-dev_1.5-5_amd64.deb
Files: 
 3f8f9113d1e61eb04298cd9881f0d996 1130 utils extra libytnef_1.5-5.dsc
 6ea1832805d1d127bf500bf53645b302 380636 utils extra libytnef_1.5-5.debian.tar.gz
 bf2ca9bdff1487dca370e54500553c06 18962 libs extra libytnef0_1.5-5_amd64.deb
 a0df24b75e1ea8ef2c9e14edd3dcd71c 23634 libdevel extra libytnef0-dev_1.5-5_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)

iEYEARECAAYFAlJWnb0ACgkQStlRaw+TLJz++wCgwSw8q8ic5LARLNzogyzLbR0/
+bAAoKpU+IxREmCz6fUNXX3CId+KKr5u
=HzYW
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: