Repository navigation
Santization issues when using part H #535
Description
MODSEC-387: At one point there was another issue for this that was closed, but I can't view it anymore to find the details. The issue is that H is so much less noisy than K, and we would like to be able to use that option. The problem is that the sanitization doesn't properly run, and sensitive data ends up in the log files that we can't have there. I know that it works with K, but it would be really really nice to be able to use the H option to reduce noise.
Activity
rcbarnett-zz commentedon Oct 17, 2013
Original reporter: abedra
fggillie commentedon Nov 18, 2020
Hello,
Is there any estimation on until when sanitising of part H will be implemented? For the moment all we can do to avoid sensitive data ending up in the logs is to remove part H when those attributes are present. Would be really nice to still have it :)
Thanks for all you are doing here!
fzipi commentedon Oct 12, 2026
Revisiting this one. This remains a 2.x bug: sanitised values still leak into audit log part H. For 3.x the situation is different: part H is not written at all yet (there is a TODO in
src/transaction.cc), so there is nothing to sanitise until that lands.Keeping it open as a 2.x bug. For 3.x it depends on part H being implemented first.