Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>So, someone got access to write to arbitrary files on your server. I assume you've cleaned up the exploit that let them in already.</p> <p>The problem is, while the <code>eval(base64_decode</code> stuff is obvious, and has to go, the intruder could have put other stuff in there. Who knows, maybe he deleted a <code>mysql_real_escape_string</code> somewhere, to leave you vulnerable to future SQL injection? Or a <code>htmlspecialchars</code>, leaving you vulnerable to JavaScript injection? Could have done anything. Might not even be PHP; you sure no JavaScript was added? Or embeds?</p> <p>The best way to be sure is to compare to a known-good copy. You do have version control and backups, right?</p> <p>Otherwise, you can indeed use <code>perl -pi -e</code> to do a substitute on that PHP code, though matching it might be difficult, depending. This might work (work on a copy!), and adjust spacing in the regexp as needed:</p> <pre><code>perl -pi -e 's!&lt;\?php eval\(base64_decode\(.*?\)\) \?&gt;!!g' *.php </code></pre> <p>but really, you should review each file by hand, to confirm there are no other exploits present. Even if your last known-good copies are somewhat old, you can review the diffs.</p> <h2>edit:</h2> <p>Ok, so it sounds like you don't want to nuke the whole PHP block, just the eval line:</p> <pre><code>perl -pi -e 's!eval\(base64_decode\(.*?\)\);!!g' *.php </code></pre> <p>You may want to add a <code>\n</code> before the first <code>!</code> if there is additionally a newline to kill, etc. If the base64 actually has newlines in it, then you will need to add <code>s</code> after the <code>g</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. PODeleting base64 Eval Junk with (osx) terminal
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USderobert
    1. USderobert
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COGood backups would have been much, much, better. But, they don't exist. They will when I'm through. And, you're absolutely right, I will have to go through by hand -- but, not having to click and drag a few thousand times will help. As it is, I get "Can't open *.php: No such file or directory." -- which is what I was getting before. This is after cd -ing to a directory that _does_ have .php files. any Ideas?
      singulars
      1. PO
      1. USMartin
    2. CO@Martin What does `echo *.php` in that directory do? Does it print *.php, or does it print a listing of them all? And, also, is this on the server, or have you copied the files to a local machine?
      singulars
      1. PO
      1. USderobert
    3. COOK -- so, the no such file was me being stupid. In the *correct* directory, hitting return gives me the nice, clean "ok tell me something else to do" line beginning (name of the comp with a : and a cursor) -- but all the files all intact.
      singulars
      1. PO
      1. USMartin
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload