SKavitapu407634 (Community Member) asked a question.
The following code got the CWE-601 issue in veracode scan report, can anyone suggest how to fix in node js?
const route = `/cc/${ci}/activity/${daid}`;
ctx.redirect(route);
Ask the Community
Get answers, share a use case, discuss your favorite features, or get input from the community.
By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.
.png){kind=logo}
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Hi @SKavitapu407634 (Community Member) ,
Veracode Static Analysis reports CWE 601 when it can see that dynamic data from outside of the application is going into the URL.
The concern being that if an attacker can influence this data they may be able to change the URL your users are sent to.
Veracode Static Analysis will only automatically close this flaw if you are able to use only hardcoded or numeric data in the URL.
If you have identifiers that are numeric you may want to cast them to a Number before including them in the URL.
If this is not possible we recommend URL encoding any path or query variables (and optionally adding validation), you can then document this for manual review using a mitigation proposal ( https://docs.veracode.com/r/improve_mitigation ) and request someone from your organizations security team to review.
Please note that URL encoding is valid only for path and query data. URL encoding as applied to hosts does not add any validation and for dynamic hosts we would recommend allow-list validation.
Thank you,
Boy Baukema
An http parameter may contain a URL value and could cause the web application to redirect the request to the specified URL. By modifying the URL value to a malicious site, an attacker may successfully launch a phishing scam and steal user credentials. Because the server name in the modified link is identical to the original site, phishing attempts have a more trustworthy appearance.