Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2008.0483 -- [Win][UNIX/Linux]
Common Data Format (CDF) Version 3.2 and earlier Buffer Overflow
9 May 2008
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: CDF 3.2 and prior
Publisher: NASA
Operating System: UNIX variants (UNIX, Linux, OSX)
Windows
Impact: Execute Arbitrary Code/Commands
Access: Remote/Unauthenticated
CVE Names: CVE-2008-2080
Original Bulletin:
http://cdf.gsfc.nasa.gov/CDF32_buffer_overflow.html
http://www.coresecurity.com/?action=item&id=2260
- --------------------------BEGIN INCLUDED TEXT--------------------
Common Data Format (CDF) Version 3.2 and earlier Buffer Overflow
Vulnerability The libraries for the scientific data file format,
Common Data Format (CDF) version 3.2 and earlier, have the potential
for a buffer overflow vulnerability when reading specially-crafted
(invalid) CDF files. If successful, this could trigger execution
of arbitrary code within the context of the CDF-reading program
that could be exploited to compromise a system, or otherwise crash
the program. While it's unlikely that you would open CDFs from
untrusted sources, we recommend everyone upgrade to the latest CDF
libraries on their systems, including the IDL and Matlab plugins.
Most worrisome is any service that enables the general public to
submit CDF files for processing.
The vulnerability is in the CDF library routines not properly
checking the length tags on a CDF file before copying data to a
stack buffer. Exploitation requires the user to explicitly open a
specially-crafted file. CDF users should not open files from untrusted
third parties until the patch is applied (and continue then to
exercise normal caution for files from untrusted third parties).
CDF 3.2.1 addresses this vulnerability and introduces further
usability fixes. Updates for Perl, IDL, Matlab and Java WebStart
are also available. Java WebStart applications that refer to
http://sscweb.gsfc.nasa.gov/skteditor/cdf/cdf-latest.jnlp, will
automatically be updated to include this fix the next time the
application is started while connected to the Internet.
Older versions of CDF have not been updated and have been moved to
the obsolete section of the CDF FTP site. The latest versions of
CDF have added support for very large files, optional pico-second
time variables (Epoch16), detection of file corruption by internal
checksum comparison, internal file compression, and performance
improvements. For compatibility with older libraries, the CDF 3.2
library can create CDF 2.7 files by calling the CDFsetFileBackward
function or setting the CDF_FILEBACKWARD environment variable (see
section 4.18 of the CDF C or Fortran Reference Manuals). Please
contact the CDF team if you still need older versions updated.
CDF 3.2.1 supports the following operating systems: OpenVMS, Windows
2000/XP/Vista, Linux, Solaris, and Mac OS X. If you need to run CDF
3.2 on other platforms, such as HP-UX or IBM AIX, please contact
the CDF team.
The CDF team greatly appreciates the efforts of Alfredo Ortega,
from CORE IMPACT's Exploit Writing Team (EWT), at Core Security
Technologies for discovering, researching and reporting this
vulnerability. Their advisory (Advisory ID: CORE-2008-0326, published
2008 May 5) is available at
http://www.coresecurity.com/?action=item&id=2260.
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
http://www.auscert.org.au/render.html?cid=1980
If you believe that your computer system has been compromised or attacked in
any way, we encourage you to let us know by completing the secure National IT
Incident Reporting Form at:
http://www.auscert.org.au/render.html?it=3192
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iQCVAwUBSCPbIih9+71yA2DNAQIK8AP+Pxeak5J+g4fwBFl2F0uAPooOhbmWdk2E
0jZ2ZDdNDYxNAurHuKiwEC+sBFLFHcI7BwuTlqpcDshay0TfLBBcoSE5/RExHDyG
vibNps1rvdmSdRXcEZNpU37aniuUPthYGGbrGeg1VQ9SEi5cZROYqdtn9jrPlDQO
ZOCDNn9lARs=
=fCah
-----END PGP SIGNATURE-----