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

Extract filename from HTTP attachment transfers #1970

Closed
neilterry10 opened this issue May 9, 2023 · 4 comments
Closed

Extract filename from HTTP attachment transfers #1970

neilterry10 opened this issue May 9, 2023 · 4 comments
Assignees

Comments

@neilterry10
Copy link

Please extract the filename from an HTTP attachment file transfer.
An example of this can be found in the ndpi pcap test file exe_download.pcap, in the source tarball 4.4-stable.zip\nDPI-4.4-stable\tests\pcap\exe_download.pcap

Here is a follow tcp stream screen show show the data needed.
image
The line "Content-Disposition: attachment; filename="phn34ycjtghm.exe"

The filename "phn34ycjtghm.exe" is what is wanted.

In this case use of the URL alone doesn't provide enough context to know what is really happening in this flow

The addition of the filename will better identify suspicious/malicious transfers. Below is an example of a download of a malicious DLL.

image

The flow risk in both these cases would show that an executable was located in the transfer, but the inclusion of the filename that has the extension .DLL makes the file transfer in the second screenshot much more suspicious and would be more helpful to an analyst.

@utoni
Copy link
Collaborator

utoni commented May 10, 2023

Thanks for pointing that out. I'll work on that.

@utoni utoni self-assigned this May 10, 2023
@lucaderi lucaderi self-assigned this Jun 13, 2023
@lucaderi
Copy link
Member

Hi @utoni I will take over this extension.

@lucaderi
Copy link
Member

Use as testing file tests/cfgs/default/pcap/exe_download.pcap

@lucaderi
Copy link
Member

Implemented by #2037

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants