Unfortunately he also released a working exploit with complete source code before the various vendors affected (Samsung, Meizu and surely others) were made aware of it, leading to a severe security issue without accessible fix for now.

I wrote then an application to circumvent the issue while manufacturer patch the security hole and publish OTA updates.

However, please note its a partial fix that cannot secure completely your device which is to date impossible without modifying it − an operation that will stop the ability to install OTAs without an external tool.

That’s why I would still recommend to consider Chainfire’s solution linked below.

Cannot protect efficiently against some potential attacks (typically, on boot).
The real fix by manufacturers or some carefully written custom kernels will indeed be the only true solutions to this vulnerability − and won’t introduce any feature regression like this one does with some firmwares on cameras.

Add missing Internet permissions for Flurry analytics:
I will likely share installation figures with my Samsung security contacts, so they get an idea of the interest generated by this kind of early fix.

Yup that’s right, Galaxy Tab 7 Plus also use an Exynos 4 platform and rocks very similar drivers.
The fixes will be released by Samsung, what I published here can more be seen as a workaround, with concrete limitations due to its “don’t modify anything” implementation.

Just wanted to say I didn’t enable this and then try the exploit app, I had done the exploit and tested both cameras, and then enabled your app and tried both cameras again, and in all cases both cameras worked on my sgs 3 gt-i9300 on stock 4.1.1 (rooted via exploit before enabling your fix for camera testing)