VAchinthalwar932395 (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 @VAchinthalwar932395 (Community Member) ,
Sometimes, even though Veracode Static Analysis has the required debug symbols, it may not know what source code line is related to a given flaw. This typically occurs with use of `public static final String` in Java and `async` in .NET. This is because the compiled output does not have enough information to relate the flaw back to the original source code line.
In these cases we recommend you review the Attack Vector reported in the details for the flaw (in the IDE plugin or in the Triage Flaws view in the Platform).
Ideally our product would report a "?" rather than "1" but unfortunately, this is a significant amount of work with our current product. Please consider registering your ideas on this with Veracode Community Ideas at https://community.veracode.com/s/ideas as this is used by Veracode Product Management to determine road map priorities.
If after that you still have remaining questions I would recommend you schedule a consultation call to discuss.
You can check out this knowledge article (https://community.veracode.com/s/article/How-to-schedule-a-consultation-call) on how to schedule a consultation call with us.
Thank you,
Boy Baukema
Hi @VAchinthalwar932395 (Community Member)
In addition to the above points mentioned by Boy.
If you have access to the Veracode platform, I would recommend reviewing the flaws from the 'Triage Flaws' page where you can see the actual Attack Vector and fine-tuned description of the particular flaw. So that will help you locate which line is getting flagged in actuality.
Regards,
Kashif