VSridharan272777 (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,
The reason CWE-297 is identified is because the TrustManager that is being used implies that it is trusting all certificates presented by services being connected to. It is recommended to use a TrustManager that validates the certificates are well-formed, signed, and follows the chain of trust, as well as verifying that the certificate matches was issued to the host being connected to. For instance, if you were connecting to "mysite.com" and the certificate presented was valid, but issued to "evil.com" then checking the Common Name against the name of the host would ensure that connection would not be considered valid.
Typically using a TrustManager that accepts all certificates is only used for testing purposes. It is not recommended to use this approach in production environments.
If you have any other questions, I would recommend you schedule a consultation call to discuss: https://help.veracode.com/r/review_main , or you can send an email to Support@veracode.com with the application and scan name so we can look into the identified flaw to provide you more specific feedback.
Regards,
Veracode Application Security Consulting Team
@arichards (Veracode) do you have any example or solved code for this issue to refer for?
The new link to the Help Center topic is https://help.veracode.com/r/review_main