For my application a security web scanner triggered a huge number of rows in APEX_DEBUG_MESSAGES by requesting wrong url pathes. The SYSAUX tablespace grew so rapidly that it almost became full. An attack on the database availability is conceivable.
Does someone have experience with this and what could be the solution? Is there a way to configure another apex debug messages behaviour?
Request examples for my app https://myhost/f?p=100 leading to APEX_DEBUG_MESSAGES entries
https://myhost/f?p=100:9999 (page not found)
https://myhost/r/hello/test (app not found)
(APEX 23.2.6, ORDS 24.1.1)