
_steviec (Community Member) asked a question.
Rather than having an ugly list of bindable properties in a controller method, it would be neater to use the Bindable(bool) attribute on the view model.

_steviec (Community Member) asked a question.
Rather than having an ugly list of bindable properties in a controller method, it would be neater to use the Bindable(bool) attribute on the view model.
Hi @_steviec (Community Member) ,
Veracode Static Analysis does not detect use of the Bindable attribute on a model property as remediation for CWE 915, but used appropriately this can be an excellent basis for a mitigation proposal ( https://help.veracode.com/r/improve_mitigation ) that you can then ask your mitigation reviewer to review.
Automatic detection of the Bindable attribute on a model property has as a potential downside that while a property may be fine in one context, it may not be in another, think of for example a Password property on a User model. While it might be perfectly fine to have this bindable in the ResetPassword action, in any other context it should likely not be bindable.
But we are actively working on better being able to detect correct and secure usage of ViewModels, so please consider registering your ideas on this with Veracode Community Ideas at https://community.veracode.com/s/ideas .
Thank you,
Boy Baukema

Thanks for your really quick response. Yes, I had thought of that too, that using the Bind attribute does allow for a finer grain of control.
As you recommend, I'll propose a mitigation.
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)
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 @_steviec (Community Member) ,
Veracode Static Analysis does not detect use of the Bindable attribute on a model property as remediation for CWE 915, but used appropriately this can be an excellent basis for a mitigation proposal ( https://help.veracode.com/r/improve_mitigation ) that you can then ask your mitigation reviewer to review.
Automatic detection of the Bindable attribute on a model property has as a potential downside that while a property may be fine in one context, it may not be in another, think of for example a Password property on a User model. While it might be perfectly fine to have this bindable in the ResetPassword action, in any other context it should likely not be bindable.
But we are actively working on better being able to detect correct and secure usage of ViewModels, so please consider registering your ideas on this with Veracode Community Ideas at https://community.veracode.com/s/ideas .
Thank you,
Boy Baukema