Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Stale
-
Affects Version/s: old
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Instructions:I have read these instructions
-
Model:i9300
-
CM Download source:
-
Radio/baseband:N/A
-
Kernel version:N/A
Description
The folks over at replicant found a backdoor in the modem which allows it to read/write/modify files on a number of devices:
http://redmine.replicant.us/projects/replicant/wiki/SamsungGalaxyBackdoor
Known affected devices:
Nexus S (I902x
Galaxy S (I9000)
Galaxy S 2 (I9100)
Galaxy Note (N7000)
Galaxy Nexus (I9250)
Galaxy Tab 2 7.0 (P31xx)
Galaxy Tab 2 10.1 (P51xx)
Galaxy S 3 (I9300)
Galaxy Note 2 (N7100)
They also mention a couple of ways to work around this:
Samsung-RIL could show a message alerting the user when the back-door is being used, including the requested path and asking the user to save logs and contact us.
Alternatively, the kernel could block the incriminated RFS requests and keep a trace of them in the logs for the record. That option would work for CyanogenMod, where the incriminated proprietary blob is still used.
Activity
bleh, I meant to except this one
Thanks! 
Regarding Dustins perspectives on the "Alphabets" with the meaning "most likely" I agree with him. It would have been nice if this got patched.
Thanks
i found fix.
https://github.com/VanirAOSP/LEGACY_device_samsung_tuna/commit/48ec5a7e71a05493a3f89b6b3e3e705b8b5e8c82
its for galxy nexus(i didnt test it but i think it working)
The device reported on is not getting cm12.0 or 12.1 nightlies and we are not planning any further cm11 snapshot releases.
If you have this issue on a cm12.0 or 12.1 SNAPSHOT please open a new report for the device you're experiencing this on and include a log and everything else. Do not clone issues as it leaves old details in the fields.
Seems legit. Recommend priority level be increased.