When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More information
Hi @APrieto034095 (Community Member),
Thanks for your question. CWE-113 is relating to the lack of cleansing of CR (carriage return) and LF (line feed) characters before the data is included in outgoing HTTP headers. The code snipped you included does not appear to set any HTTP headers. I recommend reviewing the flaw within the Triage Flaws section of the Veracode Platform for the scan in question. This will allow you to select a file to upload into your browser so you can pinpoint the exact line the flaw was found on, furthermore the attack vector, description and remediation text should be read which contains a wealth of information about where the flaw was found and how to resolve it.
To resolve CWE-113 I recommend you use a supported cleansing function that is appropriate everywhere you output HTTP headers that are constructed from untrusted data. You can find our supported cleansing functions here: https://help.veracode.com/reader/4EKhlLSMHm5jC8P8j3XccQ/IiF_rOE79ANbwnZwreSPGA.
I hope that helps.
Thanks,
Anthony Fielding