Tag Info

New answers tagged

1

Chances are, if you are having a problem with this, you may have a shell installed on your sever. Shells are php backdoors that are normally installed by an attacker through some sort of remote file inclusion vulnerability. First thing to do, is to breath and don't panic. Find the snippet of injected code in the js file and remove it. Chances are, it has ...


0

It is more likely the attacker has succeeded to install a backdoor. It is by nature hidden, and quite hard to detect and disable. You need to check some important and classic directories such as the one you use to upload images or other files because you usually trust such directories and never check what is inside them. Also, if your Joomla website has ...


1

The biggest challenge in developing secure (web) applications is implementing a secure (or security) development lifecycle process that is both effective and measurable. Enumerating all of the facets of such an undertaking is not possible here; but suffice it to say there are hundreds of books and white papers written to address the subject.


0

Apart from the OWASP top 10, I think one of the biggest challenge, related to web applications, is JavaScript Cryptography. I would highly recommend reading the following two related articles, if you're interested in exploring more about it and looking for something challenging: What’s wrong with in-browser cryptography? Javascript Cryptography Considered ...


3

It is best to plan out and control each URI (params or not) sent to the active/passive scanning engine. The target analyzer in the engagement tools (typically selected from the Target sitemap tab as "Analyze target") is a great place to select parameters and then "send to Intruder". Typically, you can customize your fault injection strategies in Intruder by ...



Top 50 recent answers are included