Open dankurka opened 9 years ago
@Brian, @Mat you probably have an opinion right here?
Reported by dankurka@google.com
on 2014-02-17 09:24:04
Accepted
Reported by dankurka@google.com
on 2014-02-17 09:25:03
We could probably fix this by checking that the class is listed in the security policy
before attempting to load it. That would still allow the attacker to deduce which classes
are in the security policy, but that doesn't seem as important since those are intentionally
client-side classes.
I'm probably not a good judge of severity; I'll defer to Matthew for that.
Reported by skybrian@google.com
on 2014-02-18 04:00:27
Reported by t.broyer
on 2014-02-18 09:31:38
Eventually this CVE http://wicket.apache.org/2014/02/21/cve-2014-0043.html might help
to classify it: information disclosure about available classes, helpful during fingerprinting
of a target
Reported by mail@Christian-Schneider.net
on 2014-02-26 00:21:57
Seems like something worth trying to fix.
Reported by mdempsky@google.com
on 2014-02-26 00:33:50
Originally reported on Google Code with ID 8580
Reported by
mail@Christian-Schneider.net
on 2014-02-16 17:37:17