Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicate file entries #7920

Open
Erik-White opened this issue Oct 11, 2024 · 3 comments
Open

Duplicate file entries #7920

Erik-White opened this issue Oct 11, 2024 · 3 comments
Labels

Comments

@Erik-White
Copy link

I have an E01 disk image of an exFAT formatted volume: LIN-exFAT.zip

Note that there is only one JPEG file on the volume:
\IX 01\Freaston\Madison\Madison\Madison\[PHOTOS]\03\049.jpg

But Sleuthkit reports the existence of two files:

\IX 01\Freaston\Madison\Madison\Madison\[PHOTOS]\03\049.jpg
\IX 01\Vikush\P2\WBC.01-100.P2\Madison\Madison\Madison \049.jpg

Potential reason for this discrepancy:

There is a deleted folder on the volume:
\IX 01\Vikush\P2\WBC.01-100.P2\

In the parent folder for the live Freaston folder, the first cluster is recorded as 1,625 stored as 0x59 0x06 (little endian) on disk in the folder structure.

In the parent folder for the deleted WBC.01-100.P2 folder, its first cluster is also 1,625. That is, the Freaston folder was created after WBC.01-100.P2 and happened to be stored at the same physical location on the volume as the previously deleted WBC.01-100.P2. Sleuthkit is mistakenly identifying both folders as the parent of the first Madison folder, and continues from that point downwards so that it appears that they both also contain 049.jpg.

Screenshot from Autopsy that shows the same problem:
image-20240925-112407

@simsong
Copy link
Member

simsong commented Oct 11, 2024

Thank you for the analysis. This is great. Do you see any solution other than reading the entire drive and then removing any allocated file from the list of unallocated files if it happens to be there?

@simsong simsong added the Bug label Oct 11, 2024
@Erik-White
Copy link
Author

Sorry I don't know enough about how Sleuthkit indexes files to offer any alternatives. That said, it sounds like a reasonable solution.

@simsong
Copy link
Member

simsong commented Oct 14, 2024

It probably needs to be done in autopsy, not in TSK. This ticket will be moved there.

@simsong simsong transferred this issue from sleuthkit/sleuthkit Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants