On: Log4Shell Log4j vulnerability (CVE-2021-44228) – c...

[mro_name]

but? It think it's far deeper than mitigation, it's the solution.

Edit: I apologize for getting 'sanitation' wrong. Don't do it.

[AnotherGoodName → mro_name]

For databases you simply parametize the inputs so that code is code and data is data and there's no mixing of the two.

Sanitization is a defence of last resort when you simply can't separate code and data. Usually used for user content on the web since HTML has no formal mechanism to separate code and data because the angled brackets that do this separation are also valid user input.

But databases do have a way to separate the query from the data. Parametize your queries.

[mro_name → AnotherGoodName]

Indeed. That's enforced system boundaries.

[jdlshore → mro_name]

The proper solution to SQL injection is parameterized queries, not input sanitization, to my knowledge.

[drunkpotato → jdlshore]

The irony here is that if you use the log4j equivalent of parameterized queries, parameterized logging strings, you're still vulnerable to this CVE, even if you did everything right.