Microsoft Compound File
m |
(→Identification) |
||
| Line 49: | Line 49: | ||
|- | |- | ||
|<code>{00020d0b-0000-0000-c000-000000000046}</code> || [[Outlook Item File]] | |<code>{00020d0b-0000-0000-c000-000000000046}</code> || [[Outlook Item File]] | ||
| + | |- | ||
| + | |<code>{00021201-0000-0000-00c0-000000000046}</code> || [[Microsoft Publisher]] | ||
|- | |- | ||
|<code>{0006f046-0000-0000-c000-000000000046}</code> || [[Outlook Item File]] | |<code>{0006f046-0000-0000-c000-000000000046}</code> || [[Outlook Item File]] | ||
Revision as of 14:14, 4 August 2018
Microsoft Compound File is a complex container format used by some versions of Microsoft Office, and other Windows-centric applications. It has features similar to those of a filesystem format.
Its name has many variations, including:
- Compound File Binary File Format (CFBF or CFB)
- Microsoft Compound Document File Format
- OLE Compound Document Format
- OLE2 Compound Document Format
- Composite Document File
The format was not publicly documented by Microsoft until 2008.
It is (or was?) unofficially known as LAOLA File Format.
Contents |
Identification
Files begin with signature bytes D0 CF 11 E0 A1 B1 1A E1.
Identifying the specific document type can be difficult. Some, but not all, document types can be identified by the CLSID field in the "root storage" directory entry. This field is usually located at file offset 512×(1 + {the 32-bit integer at offset 48}) + 80.
Some files have a stream named "<U+0005>SummaryInformation" containing metadata, which may include information about the creating application.
Root storage object CLSIDs
The table below lists some of the root storage object CLSIDs that have been observed in this type of file. Use this information at your own risk, as these identifiers can be unreliable.
Microsoft's documentation says this about the CLSID field:
This field contains an object class GUID. [...] If not [all zeroes], the object class GUID can be used as a parameter to start applications.
Although every storage object (think subdirectory) can have a CLSID, this table is only concerned with the file's root storage object.
Note that the CLSIDs are stored as GUIDs in little-endian binary format, so they have a strange byte order.
| Root storage object CLSID | Format |
|---|---|
{00000000-0000-0000-0000-000000000000} |
Unspecified (could be Thumbs.db, SUO, ...) |
{00020810-0000-0000-c000-000000000046} |
XLS |
{00020820-0000-0000-c000-000000000046} |
XLS |
{00020906-0000-0000-c000-000000000046} |
DOC |
{00020d0b-0000-0000-c000-000000000046} |
Outlook Item File |
{00021201-0000-0000-00c0-000000000046} |
Microsoft Publisher |
{0006f046-0000-0000-c000-000000000046} |
Outlook Item File |
{000c1084-0000-0000-c000-000000000046} |
MSI |
{1cdd8c7b-81c0-45a0-9fed-04143144cc1e} |
MAX (3ds Max) |
{18b8d021-b4fd-11d0-a97e-00a0c905410d} |
MIX (PhotoDraw) |
{56616700-c154-11ce-8553-00aa00a1f95b} |
FlashPix |
{56616800-c154-11ce-8553-00aa00a1f95b} |
MIX (PhotoDraw) or MIX (Picture It!) |
{64818d10-4f9b-11cf-86ea-00aa00b929e8} |
PPT |
{c65e63e1-6c0e-11cf-842e-00aa006130ba} |
Softimage SCN |
Related formats
For formats based on this format, see Category:Microsoft Compound File.
Specifications
Programs, libraries, and utilities
- Structured Storage Viewer
- libolecf
- OleFileIO_PL - a Python module to read MS OLE2 files
- oledump.py beta
- officeparser
- python-oletools - python tools to analyze OLE files
- OpenMCDF
- 7-Zip
Links
- Wikipedia article
- Forensics Wiki article
- Joel on Software: Why are the Microsoft Office file formats so complicated?
- Some (older) reverse engineered information here and a Perl module here
- Malicious Office macros are not dead
- MS Office 97-2003 legacy/binary formats security - article with lots of resources on MS Office formats, including analysis techniques, tools and parsing libraries
- MSDN: Providing Summary Information
