
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
What to do with "Mass Assignment: Insecure Binder Configuration"?
Heated discussions at my client around this relatively new (well since 2015.1) rule. "Mass Assignment: Insecure Binder Configuration"
After reading the explanantion and resolution advise most peoples response is: "yes, sure but our implementation is not so naive. we only have backing objects that only contain the fields that need to be exposed." Even the advise for fixing is a bit misleading and give a false sense of security (another place you need to update when adding fields).
So we have most teams mark these as false positives.
What do you do with them?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Same here, I have yet to see a good "fix" for this category so they get marked false positive. I have also not seen an exploit PoC for this one.
David

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Apparently these flaws are exploitable, see below. Hoping to find a solution to remedy this.
http://www.codeproject.com/Articles/471784/Exploiting-Microsoft-MVC-vulnerabilities-using-OWA