Mongo injections attempts

Tactic:

TA0043-reconnaissance

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Goal

Detect MongoDB injection attempts on web services accessing data from Mongo databases. Such security activity generally indicates that an attacker is trying to exploit a potential MongoDB injection vulnerability or steal sensitive data.

Strategy

Monitor application security events to detect NoSQL (@appsec.rule_id:(sqr-000-007 OR crs-942-290)) injection attempts on distributed traces where external MongoDB queries are performed (@_dd.appsec.enrichment.has_mongo:true).

The signal severity is determined based on the underlying service behavior:

  • HIGH Substantial rate of MongoDB injection attempts on services executing MongoDB queries, and resulting in Mongo exceptions.
  • MEDIUM High rate of SQL/CQL injection attempts on services executing MongoDB queries.

Triage and response

  1. Consider blocking the attacking IP(s) temporarily to prevent them from reaching deeper parts of your production systems.
  2. Review the 5xx errors and the other application security events detected to assess the impact on the services.
  3. Investigate if the parameters are ending up in the MongoDB query without sanitization. If they do, fix the code.