CChowdary293928 (Community Member) asked a question.
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 @CChowdary293928 (Community Member) - Our team will need more information to be able to provide remediation steps. You can schedule a consultation call with our AppSec Consulting team, using the green schedule a consultation button on the home page of the community.
We met with someone from the team to discuss this more. This is what were were told. @SamHouston (Veracode)
Hello Dan,
It was nice to assist you today with your agenda to discuss your TypeScript CWE-201 flaws. As discussed, please consider entering a mitigation proposal for these flaws to comment that the data handled here is either not sensitive and/or is getting safely transmitted in a way that does not violate security policies at your organization. Consider leveraging the bulk mitigation approach in the Triage Flaws view to update all these flaws at once with a similar mitigation proposal comment -> https://docs.veracode.com/r/Perform_Multiple_Changes_from_the_Triage_Flaws_Page .
If you would like to see the Veracode Product and static scanner support other ways to no longer report and address CWE-201 flaws aside from having to enter and approve a mitigation proposal -- for instance, other customers have raised interest in having the option to indicate trusted sources of input to not view as taint sources for reporting on certain CWEs -- then please consider raising such ideas and product feedback by making use of our Ideas form in our Veracode Community site at https://community.veracode.com/s/ideas . Note you will need to have created an account in the Community to use this form.
Please let me know how else I can be of assistance regarding this agenda.
Best regards,
Andrew// Application Security Consultant, Veracode