Some bad news is surfacing this weekend for owners of several popular Samsung devices. Members of XDA Developers identified a kernel exploit for devices with certain Exynos processors that could provide root access without flashing the device. According to XDA member alephzain, the vulnerability was discovered on his Samsung Galaxy S III in /dev/exynos-mem.
Recently discover a way to obtain root on S3 without ODIN flashing.
The security hole is in kernel, exactly with the device /dev/exynos-mem.
This device is R/W by all users and give access to all physical memory :confused: ...
You’ve read that title right folks. Only a few days after the device went on sale do we have an exploit that gives root access to the little HDMI dongle. The folks over at GTVHacker found this exploit. As you know the Chromecast is supposed to be running a simplified version of the ChromeOS however the folks at GTVHacker believe it to be more of a modified Google TV Release.
I'm using OSSEC with the web UI, and the logs keep getting the a message saying "Common web attack" with a level 6 severity. However, the source is localhost.
2012 Aug 26 19:14:27 Rule Id: 31104 level: 6
Src IP: 127.0.0.1
Common web attack.
Why is OSSEC under the impression that my computer is attacking itself?
Samsung’s upcoming Exynos 5 dual-core SoC we told you about yesterday is certainly expected to bring a new level of performance to Android devices. However, there’s the thought that the 1.7GHz chip will not only bring faster speeds, but it will also bring Retina-level displays on the various devices that are powered by the superchip.
I want to access the process control blocks of processes within my system and work with the field values. I am aware of the fact that at a user level, I will only have access to certain fields through the /proc folder. Is it possible for me to access those fields which are at the kernel level and would normally be inaccessible? Is there any API for the same?