|
|
|
<p id="poster">init</p> |
|
|
|
<script type='text/javascript'> |
|
$.getJSON('databasequery.json?preauthbatch json details',function(json){ |
|
console.log(json); |
|
var index; |
|
var para = "File Count: "+json.preauthbatch.preauthfilecount+"<br />"; |
|
para += "Stored File Count:"+json.preauthbatch.storedfilecount+"<br />"; |
|
para += "Stored Preauth: "+json.preauthbatch.storedpreauth+"<br />"; |
|
para += "Stored Capture: "+json.preauthbatch.storedpreauthcapture; |
Filename: nhpos/WEB/preauth.html
Line: 16
CWE: 117 (Improper Output Neutralization for Logs)
This call to console.log() could result in a log forging attack. Writing untrusted data into a log file allows an attacker to forge log entries or inject malicious content into log files. Corrupted log files can be used to cover an attacker's tracks or as a delivery mechanism for an attack on a log viewing or processing utility. For example, if a web administrator uses a browser-based utility to review logs, a cross-site scripting attack might be possible. Avoid directly embedding user input in log files when possible. Sanitize untrusted data used to construct log entries by using a safe logging mechanism such as the OWASP ESAPI Logger, which will automatically remove unexpected carriage returns and line feeds and can be configured to use HTML entity encoding for non-alphanumeric data. Alternatively, some of the XSS escaping functions from the OWASP Java Encoder project will also sanitize CRLF sequences. Only create a custom blocklist when absolutely necessary. Always validate untrusted input to ensure that it conforms to the expected format, using centralized data validation routines when possible. References: CWE OWASP Supported Cleansers/nDon't know how to fix this? Don't know why this was reported?
Get Assistance from Veracode
Genpos-windows//nhpos/WEB/preauth.html
Lines 11 to 21 in 06bd9b0
Filename: nhpos/WEB/preauth.html
Line: 16
CWE: 117 (Improper Output Neutralization for Logs)
This call to console.log() could result in a log forging attack. Writing untrusted data into a log file allows an attacker to forge log entries or inject malicious content into log files. Corrupted log files can be used to cover an attacker's tracks or as a delivery mechanism for an attack on a log viewing or processing utility. For example, if a web administrator uses a browser-based utility to review logs, a cross-site scripting attack might be possible. Avoid directly embedding user input in log files when possible. Sanitize untrusted data used to construct log entries by using a safe logging mechanism such as the OWASP ESAPI Logger, which will automatically remove unexpected carriage returns and line feeds and can be configured to use HTML entity encoding for non-alphanumeric data. Alternatively, some of the XSS escaping functions from the OWASP Java Encoder project will also sanitize CRLF sequences. Only create a custom blocklist when absolutely necessary. Always validate untrusted input to ensure that it conforms to the expected format, using centralized data validation routines when possible. References: CWE OWASP Supported Cleansers/nDon't know how to fix this? Don't know why this was reported?
Get Assistance from Veracode