POST-MORTEM D'INCIDENT — Analyse de cause racine et guide d'atténuation pour les équipes d'ingénierie.
flawopen.com/Incidents/MOVEit CVE-2023-34362
MOVEit Transfer : une injection SQL, des milliers d'organisations touchées
En clair (ELI5)
Une entreprise de transport gère un dépôt central ultra-sécurisé où d'autres entreprises déposent leurs colis. Un individu s'aperçoit que le formulaire d'accueil accepte des ordres secrets que le gardien exécute à la lettre — par exemple 'donnez-moi le pass général'. Piller ce seul dépôt a permis de dérober les colis de milliers d'entreprises.
The lessons that actually transfer
- ✓Parameterise every query, without exception. SQL injection has been the best-understood vulnerability class in the industry for over two decades, and it still produced one of the largest breach events of 2023. Consistency is the control; a single concatenated query is enough.
- ✓Audit by pattern, not by report. When one SQL injection is found, the correct response is to grep the codebase for every instance of query concatenation. MOVEit's follow-up CVEs illustrate what happens when a class of bug is fixed one instance at a time.
- ✓Internet-facing file transfer products need an elevated bar. An MFT server aggregates other organisations' confidential data at a public endpoint. Treat that concentration of risk explicitly — segment it, monitor it, and minimise retention.
- ✓Delete what you no longer need. Much of the damage came from files sitting on MOVEit servers long after the transfers completed. Aggressive retention limits would have shrunk the loss substantially at no security-engineering cost.
- ✓Patching is not remediation after a web shell. Applying the fix closes the entry point but leaves persistence in place. Incident response had to include hunting for planted shells and rotating anything the attacker could reach.
- ✓Map your vendors' vendors. Many organisations were breached through a service provider's MOVEit instance without running MOVEit themselves.
FAQ
Do ORMs prevent this?
Largely, when used normally — ORMs bind parameters by default. The risk returns when developers drop to raw SQL fragments or string-build a query builder's conditions, which most ORMs permit.
Would a WAF have blocked it?
Signature-based filtering catches unsophisticated payloads and can slow mass scanning, but it is routinely bypassed and was not a reliable defence here. It is a mitigation layer, not a substitute for parameterised queries.
Related reading
Sources et avis officiels