Tag Info

Hot answers tagged

25

The last line performs an eval() of function v78ZFAX() given the two parameters like so: eval(v78ZFAX($vFHLJ89, $vIIJ30Y)); That first parameter is the part that takes up the bulk of the code. It is assigned all that random-looking garbage, with . concatenating all those strings together into one long string: $vFHLJ89 = ...


19

These kinds of back-doors are polymorphic, that is they are designed to look different every time - in practice it's a waste of time trying to decipher them because they all do exactly the same thing. They take external input and they execute it. It might take input from a cookie or a post variable, and it might try and set some PHP options to prevent ...


15

You can decode the start of $_X: root@bt:~# echo -e ...


9

Yes, there are obvious flaws. Here are some: You can't make hashing slow by introducing simple delays. An attacker doesn't have to evaluate the hash the same way you did; they just need to get the same answer in the end. That means whatever is making the hash slow needs to be a necessary component of the hash -- it must be impossible to compute the hash ...


4

Have you tried including quotes to break this? From what I see here, it should actually cause a horrible error if a quote is passed in. Sometimes you have to fiddle around a little before the crash happens. $query = mysqli_query($con,"SELECT * FROM users WHERE name='$user'"); Here is my attempt to break this: 'OR 1=1-- It appears you have not used ...


4

Once you format the code a little, like how I edited your question, it's easier to see what's going on. $OOO000000=urldecode('%66%67%36%73%62%65%68%70%72%61%34%63%6f%5f%74%6e%64' translates to $OOO000000=fg6sbehpra4co_tnd All of that is used to build the string: $OOO0000O0=base64_decode The eval section is base64 encoded and resolves to: ...


3

Yes, you are completely open to SQL injection, eg via validUsername' injectionPayload %23, which would give you this query (the # (encoded as %23 cuts of the remaining '): SELECT * FROM users WHERE name='validUsername' injectionPayload #' Into Outfile depending on the rights of the user, you could write content into a file with this payload: -1' UNION ...


3

I decoded the whole code by changing the eval function to var_dump. This gave me: string(133) "$_X=base64_decode($_X);$_X=strtr($_X,'123456aouie','aouie123456');$_R=ereg_replace('__FILE__',"'".$_F."'",$_X);eval($_R);$_R=0;$_X=0;" or formatted: $_X=base64_decode($_X); $_X=strtr($_X,'123456aouie','aouie123456'); $_R=ereg_replace('__FILE__',"'".$_F."'",$_X); ...


2

As documented rather indirectly in the page for the crypt() function, the "cost" parameter is the base-2 logarithm of iteration count, or to put it another way, each +1 increase to "cost" represents a doubling of the number of iterations. If a cost-10 hash takes one minute to crack, a cost-14 would take 2^(14-10) = 16 minutes. Cracking a cryptographic has ...


1

You generally don't want to encrypt passwords as that opens the door to them being stolen. Instead you want to hash them, a one-way operation is mathematically impossible (or at least very hard) to reverse. This means that stealing password hashes will never lead to stealing passwords. PHP has a great set of functions for this: password_hash and ...


1

That's a remote command shell for a server that's probably been hacked, and you should consider the server compromised. You would be wise to suspend everything it hosts, audit all code on the machine and rebuild it / replace it. Remote users who probably control this script can force it to issue any command by posting "CODE" that's base64_encoded (that sent ...


1

no. it looks like you're using a global constant for the salt. you want it to change per user record. see http://stackoverflow.com/questions/2999197/do-i-need-a-random-salt-once-per-password-or-only-once-per-database also, @coverosgene is right - there's no point in slowing your own hash method down.


1

You are saying that the private key cannot be decrypted server-side for authentication (because then the server would need the password), and it also cannot be sent to anybody requesting it, and then decrypted client-side (because then the private key would be vulnerable to an offline brute force attack). Basically, what's left is to design a completely ...


1

The new password_hash introduced in PHP 5.5.0 creates a very strong one way hashing algorithm. All information that's needed to verify the hash is included in it. I tried running a loop for 5000 times, and every hash for a single password was a unique hash. To create a password hash you can simply use : $password = '170991'; $hash = ...


1

I know this post are old just for someone find this post on google Check about dnsbl many server are free to use I use few dnsbl server and many vpn proxy and tor are blocked on my website I recommand to keep for a specific time in a database the user ip so when he continu to visit your website he can load faster. Mine took aroud 5 to 10 second before ...



Only top voted, non community-wiki answers of a minimum length are eligible