Invicti detected that the application is vulnerable to a Time Based MongoDB injection. MongoDB injections occur when applications don't check or sanitize user input, which is then interpreted by a MongoDB database.

Invicti confirmed the vulnerability by executing test queries on the backend database. In these tests, MongoDB injection was not obvious, but the different responses from the page based on our tests allowed us to identify and confirm the MongoDB injection.

Depending on the backend database, the database connection settings, and the operating system, an attacker can mount one or more of the following attacks successfully:

• Reading, updating and deleting arbitrary data or tables from the database
• Collect sensitive information about the backend server configuration

To avoid this vulnerability;

• Sanitize and strictly check the type of user-supplied input.
• Avoid using where, mapReduce and group operators with user input.
• If possible set javascriptEnabled to false in mongod.conf.
• Use the most recent version of MongoDB.

There are numerous freely available tools to exploit SQL injection vulnerabilities. This is a complex area with many dependencies; however, it should be noted that the numerous resources available in this area have raised both attacker awareness of the issues and their ability to discover and leverage them. SQL injection is one of the most common web application vulnerabilities.

1. See the remedy for solution.
2. If you are not using a database access layer (DAL), consider using one. This will help you centralize the issue. You can also use ORM (object relational mapping). Most of the ORM systems use only parameterized queries and this can solve the whole SQL injection problem.
3. Locate the all dynamically generated SQL queries and convert them to parameterized queries. (If you decide to use a DAL/ORM, change all legacy code to use these new libraries.)
4. Use your weblogs and application logs to see if there were any previous but undetected attacks to this resource.