Using the table above, it can be seen that in the first two metadata
blocks have changed when the content has been modified in the .doc file. There
are many similarities in the first block, but the first thing that stands out
that has changed are the Modified, Accessed and Created times. The eighth byte
of this metadata block also changed, as it did on all the drives when an action
was performed on the .doc file. Each time it changed from 0D to 16.
When the folder was added to the system, this byte changed
to 15 on most occasions, except for when the .doc and .txt files were added into
the file, in which case it changed to 16.
Another change common across all the drives where a change
has occurred (except for the deleted file) is at offset 0x075011C. Originally
the byte was set to 50, but in this case (and when permissions are changed) it
was set to A0.
Further down at offset 0x0750660, where the file name can be
seen there are some very important differences. Previously, before the change,
the filename was found in this block twice, but after the content
modifications, it appeared three times.
All the MACE times changed (highlighted in green below) and
highlighted in orange is a very important difference.
When the first file was added the contents were "helloworld"
making the file size 10 bytes, which in hexadecimal is 0A. Having changed the
content to "free pizza sounds good"
the file size should have changed to 22 bytes, which in hexadecimal is 16. This
byte can be seen at offset 0x0750710. It is 16 on this drive, but on the
original one, it was set to 0A.
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17
18 19 1A 1B 1C 1D 1E 1F
000750660 6C 00 6C 00 6F 00 77 00 6F 00 72 00 6C 00 64 00 2E 00 64
00 6F 00 63 00 40 04 00 00 10 00 20 00 l.l.o.w.o.r.l.d...d.o.c.@..... .
000750680 08 00 30 00 10 04 00 00 30 00 01 00 68 00 65 00 6C 00 6C
00 6F 00 77 00 6F 00 72 00 6C 00 64 00 ..0.....0...h.e.l.l.o.w.o.r.l.d.
0007506A0 2E 00 64 00 6F 00 63 00 A8 00 00 00 28 00 01 00 00 00 00
00 10 01 00 00 10 01 00 00 02 00 00 00 ..d.o.c.¨...(...................
0007506C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 24 2F 27 6F 7F 2B D0 01 D0 5C 9D 34 87 2B D0 01 ................$/'o.+Ð.Ð\.4+Ð.
0007506E0 D0 5C 9D 34 87 2B D0 01 24 2F 27 6F 7F 2B D0 01 20 00 00 00 00 00 00 00 00 06 00 00 00 00
00 00 Ð\.4+Ð.$/'o.+Ð. ...............
000750700 02 00 00 00 00 00 00 00 2B 4F FA FB 01 00 00 00 16 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 ........+Oúû....................
000750720 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 ................................
000754740 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00
00 A0 01 00 00 D4 00 00 00 00 02 00 00 ................ ... ...Ô.......
000754760 74 02 00 00 01 00 00 00 78 02 00 00 00 00 00 00 80 01 00
00 10 00 0E 00 08 00 20 00 60 01 00 00 t.......x................ .`...
000754780 60 01 00 00 00 00 00 00 80 00 00 00 00 00 00 00 88 00 00
00 28 00 01 00 01 00 00 00 20 01 00 00 `.................(....... ...
0007547A0 20 01 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 01 00 00 00 00 00 00 00 ...............................
0007547C0 00 00 00 00 00 00 01 00 00 00 00 00 0A 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00
00 ................................
0007507E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 ................................
000750800 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 20 00 00 00 50 00 00 00 ........................ ...P...
000750820 84 00 00 00 00 02 00 00 D4 00 00 00 01 00 00 00 D8 00 00
00 00 00 00 00 30 00 00 00 10 00 10 00 .......Ô.......Ø.......0.......
000750840 00 00 10 00 20 00 00 00 00 00 00 00 00 00 00 00 04 00 00
00 00 00 00 00 AC 01 00 00 00 00 00
00 .... ...................¬.......
Highlighted above in purple is the file pointer, which when
converted is pointing to offset 0x07B0000. When this location is accessed in
hexadecimal, the contents are found here. It is show in the block below. This
is the same position as originally, before any changes to the content. This
mimics NTFS in the way that the contents are also found at the same place as
the original NTFS drive; thus overwriting the previous content.
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17
18 19 1A 1B 1C 1D 1E 1F
0007B0000 66 72 65 65 20 70 69 7A 7A 61
20 73 6F 75 6E 64 73 20 67 6F 6F 64 00 00 00 00 00 00
00 00 00 00 free pizza sounds
good..........
This is only found once in the file system and the previous
content "helloworld"
cannot be found at all. This means that if someone did not want the contents of
a file to be discovered (and they no longer wanted to use the file), they would
simply have to change the file contents, rather than delete the file, to
prevent anyone from viewing that content. This also applies on NTFS; once the
content in the file has been overwritten, it is no longer discoverable in the
hexadecimal.
At offset 0x0754000 the metadata block is almost identical
to the one investigated above, with the exceptions being the first two bytes,
the eighth byte, the Modified and Accessed times (seen in the block above) and
two values at offsets 0x07547CC and 0x07547D4 (highlighted in green) which are
set to 16 rather than 0A. As spoken about, 0A is the previous file size, so it
could be that these values represent the file size before the modifications.
The metadata block at offset 0x0758000 must be the original,
as it is identical across all drives with changes. The bytes which in the
previous block changed from 0A to 16 are still 0A and the file size is also 0A,
which is the original file size. The metadata block at offset 0x075C000 is also
the same as the original drive. This looks like it could be a block that was
created before the file was even added to the drive.
The Security Descriptor (below) is found on this drive three
times, at offsets 0x0780560, 0x0788560 and 0x078C560. It was only found twice
on the file system before the content of the file was
changed, but wasn't found at all on the blank drive.
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17
18 19 1A 1B 1C 1D 1E 1F
000780560 B8 00 00 00 10 00 5E 00 00 00 70 00 48 00 00 00 30 00 02
00 53 00 2D 00 31 00 2D 00 35 00 2D 00 ¸.....^...p.H...0...S.-.1.-.5.-.
000780580 32 00 31 00 2D 00 31 00 35 00 37 00 37 00 36 00 39 00 30
00 31 00 38 00 35 00 2D 00 31 00 39 00 2.1.-.1.5.7.7.6.9.0.1.8.5.-.1.9.
0007805A0 38 00 32 00 30 00 30 00 32 00 39 00 35 00 38 00 2D 00 33
00 32 00 35 00 31 00 33 00 31 00 38 00 8.2.0.0.2.9.5.8.-.3.2.5.1.3.1.8.
0007805C0 30 00 36 00 2D 00 31 00 30 00 30 00 31 00 00 00 02 07 00
00 00 00 00 00 00 00 00 00 00 00 00 00 0.6.-.1.0.0.1...................
0007805E0 57 4F 56 18 7F 2B D0 01 57 4F 56 18 7F 2B D0 01 57 4F 56
18 7F 2B D0 01 57 4F 56 18 7F 2B D0 01 WOV..+Ð.WOV..+Ð.WOV..+Ð.WOV..+Ð.
To further test how the content modifications affect the
drive, tests adding varying lengths of content to the files were performed. The
first one changed the .doc file's content to "byebye", the second one changed
the content to "I like dinosaurs. My
favourite is a Velociraptor and a pterodactyl."
and the final one changed the content to 63KB of filler text (lorem ipsum
).
As expected, each file's content appeared at the same offset
(0x07B0000) as was show in earlier tests (shown below).
"byebye"
content:
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17
18 19 1A 1B 1C 1D 1E 1F
0007B0000 62 79 65 62 79 65 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 byebye..........................
Paragraph
content:
0007B0000 49 20 6C 69 6B 65 20 64 69 6E 6F 73 61 75 72 73 2E 20 4D
79 20 66 61 76 6F 75 72 69 74 65 20 69 I
like dinosaurs. My favourite i
0007B0020 73 20 61 20 56 65 6C 6F 63 69 72 61 70 74 6F 72 20 61 6E
64 20 61 20 70 74 65 72 6F 64 61 63 74 s
a Velociraptor and a pterodact
0007B0040 79 6C 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 yl..............................
63KB
of filler text as content:
0007B0000 45 58 41 4D 50 4C 45 20 54 45 58 54 20 42 45 47 49 4E 0D
0A 4C 6F 72 65 6D 20 69 70 73 75 6D 20 EXAMPLE TEXT BEGIN..Lorem ipsum
0007B0020 64 6F 6C 6F 72 20 73 69 74 20 61 6D 65 74 2C 20 63 6F 6E
73 65 63 74 65 74 75 72 20 61 64 69 70 dolor sit amet, consectetur
adip
0007B0040 69 73 63 69 6E 67 20 65 6C 69 74 2E 20 50 72 61 65 73 65
6E 74 20 73 63 65 6C 65 72 69 73 71 75 iscing elit. Praesent
scelerisqu
~~~~~~~~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~
~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
0007BFE00 69 61 74 20 6E 75 6E 63 20 63 6F 6E 76 61 6C 6C 69 73 2E 20 41 6C 69 71 75 61 6D 20 76 65 6E 65 iat nunc convallis. Aliquam vene
0007BFE20 6E 61 74 69 73 20 6A 75 73 74 6F 20 69 6E 20 6E 69 73 6C
20 74 69 6E 63 69 64 75 6E 74 20 73 65 natis justo in nisl tincidunt se
0007BFE40 6D 70 65 72 2E 20 0D 0A 45 58 41 4D 50 4C 45 20 54 45 58
54 20 45 4E 44 00 00 00 00 00 00 00 00 mper. ..EXAMPLE TEXT END........
On each drive, as has become familiar, the byte at offset
0x0750008 changed from 0D to 16 and the byte at 0x075011C changed from 50 to
A0. MACE times were other bytes which differed between the drives, but the
bytes AC 74 C5 C1 01 at offset 0x07501B0 remained the same across each drive.
The bytes starting at offset 0x0750710 vary between each
drive, because this is the file size. On the drive where the file contents are "free pizza sounds good" this byte is 16
(in decimal this is 22). When the contents were changed to "byebye" this byte became 06 as
the file contents is 6 bytes long. On the drive where the paragraph ("I like dinosaurs. My favourite is a
Velociraptor and a pterodactyl.") has
been added the byte became 43 (highlighted in orange below), which is 67 bytes in decimal.
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17
18 19 1A 1B 1C 1D 1E 1F
0007506C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 24 2F 27
6F 7F 2B D0 01 30 ED 8D A8 65 41 D0 01 ................$/'o.+Ð.0í.¨eAÐ.
0007506E0 30 ED 8D A8 65 41 D0 01 24 2F 27 6F 7F 2B D0 01 20 00 00
00 00 00 00 00 00 06 00 00 00 00 00 00 0í.¨eAÐ.$/'o.+Ð.
...............
000750700 02 00 00 00 00 00 00 00 2B 4F FA FB 01 00 00 00 43 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 ........+Oúû....C...............
000750720 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 ................................
Finally, where the large amount of filler text has been
pasted into the file, two bytes at this offset have been used and set to 58 FE
(highlighted in orange below). In big endian this is FE 58, which is 65,112 in
decimal. When this value is divided by 1,024, the result is 63. This is the
number of kilobytes the file is. The original file size (0A) seems to remain at
offsets 0x07507CC and 0x07507D4 (highlighted in red).
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E
0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F
0007506C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 24 2F 27
6F 7F 2B D0 01 9E E8 0C E9 66 41 D0 01 ................$/'o.+Ð.è.éfAÐ.
0007506E0 9E E8 0C E9 66 41 D0 01 24 2F 27 6F 7F 2B D0 01 20 00 00
00 00 00 00 00 00 06 00 00 00 00 00 00 è.éfAÐ.$/'o.+Ð. ...............
000750700 02 00 00 00 00 00 00 00 2B 4F FA FB 01 00 00 00 58 FE 00 00 00 00 00 00 00 00 01 00 00 00 00 00 ........+Oúû....Xþ..............
000750720 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 ................................
000750720 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 ................................
000750740 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00
00 A0 01 00 00 D4 00 00 00 00 02 00 00 ................ ... ...Ô.......
000750760 74 02 00 00 01 00 00 00 78 02 00 00 00 00 00 00 80 01 00
00 10 00 0E 00 08 00 20 00 60 01 00 00 t.......x................ .`...
000750780 60 01 00 00 00 00 00 00 80 00 00 00 00 00 00 00 88 00 00
00 28 00 01 00 01 00 00 00 20 01 00 00 `.................(....... ...
0007507A0 20 01 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 01 00 00 00 00 00 00 00 ...............................
0007507C0 00 00 00 00 00 00 01 00 00 00 00 00 0A 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00
00 ................................
At the next metadata block however, the bytes shown above
which hold the original file size are changed and hold the current file size
(58 FE). Doing it this way allows the file system to keep track of the
original/previous file size, although there is no record of the previous file
contents.