Difference between pages "JTAG and Chip-Off Tools and Equipment" and "Windows Prefetch File Format"

From Forensics Wiki
(Difference between pages)
Jump to: navigation, search
 
(Format version)
 
Line 1: Line 1:
The following list contains equipment used for performing JTAG and chip-off analysis.  It is noted when equipment is used for both procedures in order to avoid overlap and duplication of equipment.  The URL's provided are for reference and other vendors and suppliers exist for said equipment.  Please search Internet for other competitive vendors.
+
{{expand}}
  
''Note: This equipment is not a definitive list and substitutions can be made for equivalent tools and equipment.''
+
A Windows Prefetch file consists of one file header and multiple file sections with different content. Not all content has an obvious forensic value.
  
'''JTAG and Chip-Off Equipment List'''
+
As far as have been possible to ascertain, there is no public description of the format. The description below has been synthesised from examination
 +
of multiple prefetch files.
 +
 
 +
== Characteristics ==
 +
Integer values are stored in little-endian.
 +
 
 +
Strings are stored as UTF-16 little-endian without a byte-order-mark (BOM).
 +
 
 +
Timestamps are stored as Windows Filetime in UTC.
 +
 
 +
== Header ==
 +
 
 +
This format has been observed on Windows XP, ...  will need to be modified for Vista/Win7 format
  
 
{| class="wikitable"
 
{| class="wikitable"
! align="left"| Item
 
! Info
 
! Estimated Cost (CAD)
 
 
|-
 
|-
|Carton SPZT-50PG Microscope
+
! Field
|http://www.carton.ca/p1SPZ-PG.html
+
! Offset
|$1400
+
! Length
 +
! Type
 +
! Notes
 
|-
 
|-
|Xytronic 988D Solder Rework Station
+
| H1
|http://www.howardelectronics.com/xytronic/988d.html
+
| 0x0000
|$300
+
| 4
 +
| DWORD
 +
| Format version (see format version section below)
 
|-
 
|-
|Xytronic LF-852D Hot Air Station
+
| H2
|http://www.howardelectronics.com/xytronic/LF-852D.html
+
| 0x0004
|$225
+
| 4
 +
| DWORD
 +
| Signature 'SCCA' (or in hexadecimal representation 0x53 0x43 0x43 0x4)
 
|-
 
|-
|HP Agilent U8002A Variable Power Supply
+
| H3
|http://www.home.agilent.com/agilent/product.jspx?pn=u8002a&cc=CA&lc=eng
+
| 0x0008
|$400
+
| 4
 +
| DWORD?
 +
| Unknown - Values observed: 0x0F - Windows XP, 0x11 - Windows 7, Windows 8.1
 
|-
 
|-
|Magnifying Desk Lamp
+
| H4
|http://www.amazon.com/Ultra-Efficient-LED-Magnifier-Lamp-Adjustable/dp/B001064VTE
+
| 0x000C
|$100
+
| 4
 +
| DWORD
 +
| Prefetch file length.
 
|-
 
|-
|Circuit board holder
+
| H5
|http://www.ibreakityoufixit.com/shop/mounting-kit
+
|0x0010
|$13
+
| 60
 +
| USTR
 +
| Name of executable as Unicode string, truncated after 29 characters, if necessary, and terminated by an end-of-string character (U+0000). As it appears in the prefetch file file name.
 
|-
 
|-
|Chip Epoxy Glue Remover
+
| H6
|http://www.ebay.com/itm/BGA-IC-30ml-IC-BGA-CPU-Chip-Epoxy-Glue-Remover-Adhesive-Solution-Solvent-Liquid-/321012736931?pt=Digital_Camera_Accessories&hash=item4abdd9a3a3
+
|0x004C
|$10
+
|4
 +
|DWORD
 +
|The prefetch hash, as it appears in the prefetch file name.
 
|-
 
|-
|0.040 gauge transformer winding wire
+
| H7
|sourced locally (Electronics shop)
+
|0x0050
|$15
+
|4
 +
|?
 +
| Unknown (flags)? Values observed: 0 for almost all prefetch files (XP); 1 for NTOSBOOT-B00DFAAD.pf (XP)
 
|-
 
|-
|Kester 44 rosin flux solder
+
|}
|sourced locally (Electronics shop)
+
 
|$50
+
The following part of the header is version dependent. Below the structure for format version 17.
 +
 
 +
{| class="wikitable"
 
|-
 
|-
|Xcelite Hobby Knives
+
! Field
|sourced locally (Electronics shop)
+
! Offset
|$15
+
! Length
 +
! Type
 +
! Notes
 
|-
 
|-
|Terra Dexterity PVC foam gloves
+
| H8
|sourced locally (Costco)
+
| 0x0054
|$10
+
| 4
 +
| DWORD
 +
| Offset to section A
 +
|-
 +
| H9
 +
| 0x0058
 +
| 4
 +
| DWORD
 +
| ? Nr of entries in section A
 +
|-
 +
| H10
 +
| 0x005C
 +
| 4
 +
| DWORD
 +
| Offset to section B
 +
|-
 +
| H11
 +
| 0x0060
 +
| 4
 +
| DWORD
 +
| Nr of entries in section B
 +
|-
 +
| H12
 +
| 0x0064
 +
| 4
 +
| DWORD
 +
| Offset to section C
 +
|-
 +
| H13
 +
| 0x0068
 +
| 4
 +
| DWORD
 +
| Length of section C
 +
|-
 +
| H14
 +
| 0x006C
 +
| 4
 +
| DWORD
 +
| Offset to section D
 +
|-
 +
| H15
 +
| 0x0070
 +
| 4
 +
| DWORD
 +
| ? Probably the number of entries in the D section header
 +
|-
 +
| H16
 +
| 0x0074
 +
| 4
 +
| DWORD
 +
| Length of section D
 +
|-
 +
| H17
 +
| 0x0078
 +
| 8
 +
| FTIME
 +
| Latest execution time of executable (FILETIME)
 +
|-
 +
| H18
 +
| 0x0080
 +
| 16
 +
| ?
 +
| ? Possibly structured as 4 DWORD. Observed values: /0x00000000 0x00000000 0x00000000 0x00000000/, /0x47868c00 0x00000000 0x47860c00 0x00000000/
 +
|-
 +
| H19
 +
| 0x0090
 +
| 4
 +
| DWORD
 +
| Execution counter
 +
|-
 +
| H20
 +
| 0x0094
 +
| 4
 +
| DWORD?
 +
| ? Observed values: 1, 2, 3, 4, 5, 6 (XP)
 
|-
 
|-
|8" x 8" x 3/8" steel plate
 
|sourced locally (Steel fabrication shop)
 
|free
 
 
|}
 
|}
  
'''JTAG Specific Equipment List'''
+
It's worth noting that the name of a carved prefetch file can be restored using the information in field H5 and H6, and its size can be determined by field H4.
 +
 
 +
=== Format version ===
  
 
{| class="wikitable"
 
{| class="wikitable"
! align="left"| Item
 
! Info
 
! Estimated Cost (CAD)
 
 
|-
 
|-
|RIFF Box
+
! Value
|http://www.multi-com.pl/index.php/en_US,details,id_pr,7883,menu_mode,categories.html
+
! Windows version
|$120
+
|-
 +
| 17 (0x11)
 +
| Windows XP, Windows 2003
 +
|-
 +
| 23 (0x17)
 +
| Windows Vista, Windows 7
 +
|-
 +
| 26 (0x1a)
 +
| Windows 8.1 (note this could be Windows 8 as well but has not been confirmed)
 
|-
 
|-
|Octoplus Box
 
|http://gsmserver.com/shop/gsm/octoplus_box_full_set.php
 
|$340
 
 
|}
 
|}
  
 +
== Section A ==
 +
This section contains an array with 20 byte (version 17) or 32 byte (version 23 and 26) entry records.
  
'''Chip-Off Specific Equipment List'''
+
The actual format and usage of these entry records is currently not known.
 +
 
 +
== Section B ==
 +
This section contains an array with 12 byte (version 17, 23 and 26) entry records.
 +
 
 +
The actual format and usage of these entry records is currently not known.
 +
 
 +
== Section C ==
 +
This section contains an array of UTF-16 little-endian formatted strings with end-of-string characters (U+0000).
 +
 
 +
At the end of the section there seems to be alignment padding that can contain remnant values.
 +
 
 +
== Section D - Volume information (block) ==
 +
 
 +
Section D contains one or more subsections. The number is (most likely) determined by the DWORD at file offset 0x0070. Each subsection refers to directories on an identified volume.
 +
 
 +
In this section, all offsets are assumed to be counted from the start of the D section.
 +
 
 +
The following values are version dependent. Below the structure for format version 17.
  
 
{| class="wikitable"
 
{| class="wikitable"
! align="left"| Item
 
! Info
 
! Estimated Cost (CAD)
 
 
|-
 
|-
|Wagner HT1000 Heat Gun
+
! Field
|http://www.wagnerspraytech.com/portal/ht1000_en_spray,362096,358970.html
+
! Offset
|$30
+
! Length
 +
! Type
 +
! Notes
 
|-
 
|-
|Heat Gun stand
+
| DH1
|http://www.ibreakityoufixit.com/shop/air-gun-holder
+
| +0x0000
|$60
+
| 4
 +
| DWORD
 +
| Offset to volume string (Unicode, terminated by U+0000)
 
|-
 
|-
|UP-828 Programmer
+
| DH2
|http://www.up48.com/english/programmer/up828.htm
+
| +0x0004
|$1300 - $1700 depending on source
+
| 4
 +
| DWORD
 +
| Length of volume string (nr of characters, including terminating U+0000)
 
|-
 
|-
|UP-828 SBGA152 Adapter
+
| DH3
|BlackBerry
+
| +0x0008
|$600 - $1000 depending on source
+
| 8
 +
| FTIME
 +
| (File time)
 
|-
 
|-
|UP-828 BGA110 Adapter
+
| DH4
|
+
| +0x0010
|$600 - $1000 depending on source
+
| 4
 +
| DWORD
 +
| Volume serial number of volume indicated by volume string
 
|-
 
|-
|UP-828 VBGA169E Adapter
+
| DH5
| BlackBerry and Android
+
| +0x0014
|$600 - $1000 depending on source
+
| 4
 +
| DWORD
 +
| ? Offset to section DHS1
 
|-
 
|-
|UP-828 VBGA133 Adapter
+
| DH6
|iPhone 4
+
| +0x0018
|$600 - $1000 depending on source
+
| 4
 +
| DWORD
 +
| ? Length of section DHS1 (in bytes)
 +
|-
 +
| DH7
 +
| +0x001C
 +
| 4
 +
| DWORD
 +
| ? Offset to section DHS2
 +
|-
 +
| DH8
 +
| +0x0020
 +
| 4
 +
| DWORD
 +
| ? Nr of strings in section DHS2
 +
|-
 +
| ?
 +
| +0x0024
 +
| ?
 +
| ?
 +
| ? additional 28 bytes (includes one timestamp?)
 
|}
 
|}
  
'''Notes'''
+
If all the executables and libraries referenced in the C section are from one single disk volume, there will be only one section in the D section. If multiple volumes are referenced by section C, section D will contain multiple sections.  (A simple way to force this situation is to copy, say, NOTEPAD.EXE to a USB drive, and start it from that volume. The corresponding prefetch file will have one D header referring to, e.g. \DEVICE\HARDDISK1\DP(1)0-0+4 (the USB drive), and one to, e.g. \DEVICE\HARDDISKVOLUME1\ (where the .DLLs and other support files were found).
 +
 
 +
== See Also ==
 +
* [[Prefetch]]
  
1. The UP-828 driver is not signed and therefore doesn't work by default in Windows 7 64-bit. The programmer is identified as a as a Cypess Semiconductor Corp. CY7C68013. The signed Windows 7 64-bit driver can be installed by downloading and installing the Cypress EZ-USB FX2LP Development Kit, then using the CyUSB.sys driver found in '<installdir>\CY3684_EZ-USB_FX2LP_DVK\1.0\Drivers\cyusbfx1_fx2lp' for the UP-828 programmer.
+
== External Links ==

Revision as of 01:11, 21 October 2013

Information icon.png

Please help to improve this article by expanding it.
Further information might be found on the discussion page.

A Windows Prefetch file consists of one file header and multiple file sections with different content. Not all content has an obvious forensic value.

As far as have been possible to ascertain, there is no public description of the format. The description below has been synthesised from examination of multiple prefetch files.

Contents

Characteristics

Integer values are stored in little-endian.

Strings are stored as UTF-16 little-endian without a byte-order-mark (BOM).

Timestamps are stored as Windows Filetime in UTC.

Header

This format has been observed on Windows XP, ... will need to be modified for Vista/Win7 format

Field Offset Length Type Notes
H1 0x0000 4 DWORD Format version (see format version section below)
H2 0x0004 4 DWORD Signature 'SCCA' (or in hexadecimal representation 0x53 0x43 0x43 0x4)
H3 0x0008 4 DWORD? Unknown - Values observed: 0x0F - Windows XP, 0x11 - Windows 7, Windows 8.1
H4 0x000C 4 DWORD Prefetch file length.
H5 0x0010 60 USTR Name of executable as Unicode string, truncated after 29 characters, if necessary, and terminated by an end-of-string character (U+0000). As it appears in the prefetch file file name.
H6 0x004C 4 DWORD The prefetch hash, as it appears in the prefetch file name.
H7 0x0050 4 ? Unknown (flags)? Values observed: 0 for almost all prefetch files (XP); 1 for NTOSBOOT-B00DFAAD.pf (XP)

The following part of the header is version dependent. Below the structure for format version 17.

Field Offset Length Type Notes
H8 0x0054 4 DWORD Offset to section A
H9 0x0058 4 DWORD  ? Nr of entries in section A
H10 0x005C 4 DWORD Offset to section B
H11 0x0060 4 DWORD Nr of entries in section B
H12 0x0064 4 DWORD Offset to section C
H13 0x0068 4 DWORD Length of section C
H14 0x006C 4 DWORD Offset to section D
H15 0x0070 4 DWORD  ? Probably the number of entries in the D section header
H16 0x0074 4 DWORD Length of section D
H17 0x0078 8 FTIME Latest execution time of executable (FILETIME)
H18 0x0080 16  ?  ? Possibly structured as 4 DWORD. Observed values: /0x00000000 0x00000000 0x00000000 0x00000000/, /0x47868c00 0x00000000 0x47860c00 0x00000000/
H19 0x0090 4 DWORD Execution counter
H20 0x0094 4 DWORD?  ? Observed values: 1, 2, 3, 4, 5, 6 (XP)

It's worth noting that the name of a carved prefetch file can be restored using the information in field H5 and H6, and its size can be determined by field H4.

Format version

Value Windows version
17 (0x11) Windows XP, Windows 2003
23 (0x17) Windows Vista, Windows 7
26 (0x1a) Windows 8.1 (note this could be Windows 8 as well but has not been confirmed)

Section A

This section contains an array with 20 byte (version 17) or 32 byte (version 23 and 26) entry records.

The actual format and usage of these entry records is currently not known.

Section B

This section contains an array with 12 byte (version 17, 23 and 26) entry records.

The actual format and usage of these entry records is currently not known.

Section C

This section contains an array of UTF-16 little-endian formatted strings with end-of-string characters (U+0000).

At the end of the section there seems to be alignment padding that can contain remnant values.

Section D - Volume information (block)

Section D contains one or more subsections. The number is (most likely) determined by the DWORD at file offset 0x0070. Each subsection refers to directories on an identified volume.

In this section, all offsets are assumed to be counted from the start of the D section.

The following values are version dependent. Below the structure for format version 17.

Field Offset Length Type Notes
DH1 +0x0000 4 DWORD Offset to volume string (Unicode, terminated by U+0000)
DH2 +0x0004 4 DWORD Length of volume string (nr of characters, including terminating U+0000)
DH3 +0x0008 8 FTIME (File time)
DH4 +0x0010 4 DWORD Volume serial number of volume indicated by volume string
DH5 +0x0014 4 DWORD  ? Offset to section DHS1
DH6 +0x0018 4 DWORD  ? Length of section DHS1 (in bytes)
DH7 +0x001C 4 DWORD  ? Offset to section DHS2
DH8 +0x0020 4 DWORD  ? Nr of strings in section DHS2
 ? +0x0024  ?  ?  ? additional 28 bytes (includes one timestamp?)

If all the executables and libraries referenced in the C section are from one single disk volume, there will be only one section in the D section. If multiple volumes are referenced by section C, section D will contain multiple sections. (A simple way to force this situation is to copy, say, NOTEPAD.EXE to a USB drive, and start it from that volume. The corresponding prefetch file will have one D header referring to, e.g. \DEVICE\HARDDISK1\DP(1)0-0+4 (the USB drive), and one to, e.g. \DEVICE\HARDDISKVOLUME1\ (where the .DLLs and other support files were found).

See Also

External Links