Your message dated Sat, 26 Nov 2016 15:19:28 +0000
with message-id <[email protected]>
and subject line Bug#845301: fixed in hdf5 1.10.0-patch1+docs-1~exp5
has caused the Debian Bug report #845301,
regarding hdf5: CVE-2016-4330 CVE-2016-4331 CVE-2016-4332 CVE-2016-4333
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 [email protected]
immediately.)
--
845301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845301
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: hdf5
Version: 1.8.16+docs-8
Severity: grave
Tags: security upstream
Justification: user security hole
Hi,
the following vulnerabilities were published for hdf5.
CVE-2016-4330[0]:
| In the HDF5 1.8.16 library's failure to check if the number of
| dimensions for an array read from the file is within the bounds of the
| space allocated for it, a heap-based buffer overflow will occur,
| potentially leading to arbitrary code execution.
CVE-2016-4331[1]:
| When decoding data out of a dataset encoded with the H5Z_NBIT
| decoding, the HDF5 1.8.16 library will fail to ensure that the
| precision is within the bounds of the size leading to arbitrary code
| execution.
CVE-2016-4332[2]:
| The library's failure to check if certain message types support a
| particular flag, the HDF5 1.8.16 library will cast the structure to an
| alternative structure and then assign to fields that aren't supported
| by the message type and the library will write outside the bounds of
| the heap buffer. This can lead to code execution under the context of
| the library.
CVE-2016-4333[3]:
| The HDF5 1.8.16 library allocating space for the array using a value
| from the file has an impact within the loop for initializing said
| array allowing a value within the file to modify the loop's
| terminator. Due to this, an aggressor can cause the loop's index to
| point outside the bounds of the array when initializing it.
If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2016-4330
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4330
[1] https://security-tracker.debian.org/tracker/CVE-2016-4331
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4331
[2] https://security-tracker.debian.org/tracker/CVE-2016-4332
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4332
[3] https://security-tracker.debian.org/tracker/CVE-2016-4333
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4333
Please adjust the affected versions in the BTS as needed.
Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: hdf5
Source-Version: 1.10.0-patch1+docs-1~exp5
We believe that the bug you reported is fixed in the latest version of
hdf5, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Gilles Filippini <[email protected]> (supplier of updated hdf5 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 24 Nov 2016 23:30:44 +0100
Source: hdf5
Binary: libhdf5-100 libhdf5-cpp-100 libhdf5-dev libhdf5-openmpi-100
libhdf5-openmpi-dev libhdf5-mpich-100 libhdf5-mpich-dev libhdf5-mpi-dev
libhdf5-doc hdf5-helpers hdf5-tools libhdf5-serial-dev
Architecture: source
Version: 1.10.0-patch1+docs-1~exp5
Distribution: experimental
Urgency: medium
Maintainer: Debian GIS Project <[email protected]>
Changed-By: Gilles Filippini <[email protected]>
Description:
hdf5-helpers - Hierarchical Data Format 5 (HDF5) - Helper tools
hdf5-tools - Hierarchical Data Format 5 (HDF5) - Runtime tools
libhdf5-100 - Hierarchical Data Format 5 (HDF5) - runtime files - serial versio
libhdf5-cpp-100 - Hierarchical Data Format 5 (HDF5) - C++ libraries
libhdf5-dev - Hierarchical Data Format 5 (HDF5) - development files - serial ve
libhdf5-doc - Hierarchical Data Format 5 (HDF5) - Documentation
libhdf5-mpi-dev - Hierarchical Data Format 5 (HDF5) - development files -
default M
libhdf5-mpich-100 - Hierarchical Data Format 5 (HDF5) - runtime files - MPICH2
versio
libhdf5-mpich-dev - Hierarchical Data Format 5 (HDF5) - development files -
MPICH ver
libhdf5-openmpi-100 - Hierarchical Data Format 5 (HDF5) - runtime files -
OpenMPI versi
libhdf5-openmpi-dev - Hierarchical Data Format 5 (HDF5) - development files -
OpenMPI v
libhdf5-serial-dev - transitional dummy package
Closes: 845301
Changes:
hdf5 (1.10.0-patch1+docs-1~exp5) experimental; urgency=medium
.
* New patches CVE-2016-433*.patch from upstream develop branch
to fix four vulnerabilities unveiled by TALOS (closes: #845301,
CVE-2016-4330, CVE-2016-4331, CVE-2016-4332, CVE-2016-4333)
Checksums-Sha1:
937655eb9c344f90c8575aea858158097088a3f6 2545
hdf5_1.10.0-patch1+docs-1~exp5.dsc
30346524e1fba2b1c4b29cc23b1fbfd19326c1fb 118540
hdf5_1.10.0-patch1+docs-1~exp5.debian.tar.xz
Checksums-Sha256:
a11c485ab178cd5448c518aeb30669c7f9802c326ec72d12818bf448aa535c47 2545
hdf5_1.10.0-patch1+docs-1~exp5.dsc
ecdc02f877c10859d165c11edb2ea327bff5e94770be8bc5ce65f8cded1ac231 118540
hdf5_1.10.0-patch1+docs-1~exp5.debian.tar.xz
Files:
f4bb9ef1c54fd6baf8a467247da26edb 2545 science optional
hdf5_1.10.0-patch1+docs-1~exp5.dsc
7f9f683d8a7819df1f012f26be9e0e75 118540 science optional
hdf5_1.10.0-patch1+docs-1~exp5.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQEtBAEBCAAXBQJYOaFrEBxwaW5pQGRlYmlhbi5vcmcACgkQ7+hsbH/+z4P6jQf8
DiurBTcwi3/1hsaVyF3eP9+hYrs7HRt5QHJX5cGEIj09wXv5PSGPXbIyKPpQrT+n
IvJ5TKYxvD0EcbRlFXvsK4q5pzZS8fovVaw5UoEC6ceS3rR8aFz5OpanInZQzonT
dO22dGlHEpgEBznKhhRwdHGw8mbLjocvc47UEWaJjDtihZOPnRfaY6vU4R6F19Hv
xYVIkklyg18lQWCftRztPFbUhb/fKURuKtIWot4EDNDQmIatnHM1eQFU9QXssXuV
JaXHLTxd0lS71hA33JjebdZ+foPTUgcIGhsfvgHncELiLdGzpj46/tO1pXxPPMUy
hRqjw+MnI4+2LhZljCx2Og==
=A4FI
-----END PGP SIGNATURE-----
--- End Message ---
