←back to thread

98 points shlomo_z | 1 comments | | HN request time: 0s | source
Show context
andreareina ◴[] No.45320414[source]
The normal file doesn't look that normal
replies(1): >>45356511 #
o11c ◴[] No.45356511[source]
Keep in mind that the stated use is cache-poisoning of automated scanners, not fooling humans.
replies(1): >>45357770 #
slow_typist ◴[] No.45357770[source]
Humans have to put the so called php-file on the server intentionally for any subsequent attack to work. But it is a binary file.
replies(1): >>45357920 #
h33t-l4x0r ◴[] No.45357920{3}[source]
I imagine it's supposed to get onto the server by an exploited vulnerable image upload plugin
replies(1): >>45359406 #
1. slow_typist ◴[] No.45359406{4}[source]
Maybe I don’t understand the scenario fully, but under your assumption there is no need to inject the malicious webshell later.