<?xml version="1.0"?>
<rss version="2.0">
    <channel>
        <title>OpenRCE: Blog</title>
        <link>http://www.openrce.org/rss/feeds/blog</link>
        <description>OpenRCE: The Open Reverse Code Engineering Community</description>
                <item>
            <title>Remote Code Execution - Android 2.0, 2.1</title>
                            <pubDate>Sat, 06 Nov 2010 13:01:59 -0500</pubDate>
                                        <link>https://www.openrce.org/blog/view/1619/Remote_Code_Execution_-_Android_2.0,_2.1</link>
                                        <author>DelightedZuk &lt;email-suppressed@example.com&gt;</author>
                                                    <description>Webkit on Android 2.0, 2.1, is vulnerable to use-after-free vulnerability.&lt;br /&gt;
&lt;br /&gt;
enjoy: &lt;a href=&quot;http://twitter.com/ihackbanme/status/956024508911616&quot;&gt;Blog post&lt;/a&gt;</description>
                    </item>
                <item>
            <title>Aurora, hooking, advisories, security, RE, life - my blog</title>
                            <pubDate>Mon, 19 Apr 2010 14:16:55 -0500</pubDate>
                                        <link>https://www.openrce.org/blog/view/1556/Aurora,_hooking,_advisories,_security,_RE,_life_-_my_blog</link>
                                        <author>DelightedZuk &lt;email-suppressed@example.com&gt;</author>
                                                    <description>Hey guys,&lt;br /&gt;
When I first posted this blog, it had only 1-2 lame posts, now I got much more security oriented posts.&lt;br /&gt;
My blog is about security research (I still got some security advisories I'm going to release after vendor will patch it),&lt;br /&gt;
Reverse Engineering, Aurora related original information, Hooking, programming, malware &amp;amp; hacking!&lt;br /&gt;
I'm also a member of security group who research malware, so I get very interesting samples! :]&lt;br /&gt;
&lt;br /&gt;
All the content is more-or-less is original, no copying of other posts.&lt;br /&gt;
You're all invited to view, comment and sign up as followers.&lt;br /&gt;
Thanks!&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;http://bit.ly/bRUtHw&quot;&gt;http://imthezuk.blogspot.com&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Cheers!&lt;br /&gt;
&lt;br /&gt;
</description>
                    </item>
                <item>
            <title>Administrator account VS. SYSTEM account</title>
                            <pubDate>Sun, 17 Jan 2010 04:34:28 -0600</pubDate>
                                        <link>https://www.openrce.org/blog/view/1542/Administrator_account_VS._SYSTEM_account</link>
                                        <author>DelightedZuk &lt;email-suppressed@example.com&gt;</author>
                                                    <description>Full blog post including a bit sarcasm at : &lt;a href=&quot;http://imthezuk.blogspot.com/&quot;&gt;http://imthezuk.blogspot.com/&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
I've encountered one trojan who ran already as Administrator and tried to run privilege escalation exploit against himself, so he can run as SYSTEM.&lt;br /&gt;
This is what made me write this post :&lt;br /&gt;
&lt;br /&gt;
Let's say there are 2 programs vulnerable to remote-code-execution bug.&lt;br /&gt;
1. One is running as SYSTEM&lt;br /&gt;
2. One is running as Administrator.&lt;br /&gt;
&lt;br /&gt;
Little pre-post-information regarding exploitation : If you run your exploit against a process which runs as Administrator, Your payload will run as Administrator. If you run it against SYSTEM account your payload will run as SYSTEM account.&lt;br /&gt;
&lt;br /&gt;
Which one you would want to exploit more?&lt;br /&gt;
95% of security people, will say : &amp;quot;the SYSTEM one, off-course SYSTEM is much stronger than admin, it's the strongest user in the OS&amp;quot;.&lt;br /&gt;
I'd say : it doesn't matter and I might slightly want to run as Admin instead of System. Why? This is what this blog-post is all about.&lt;br /&gt;
&lt;br /&gt;
pre Windows 2008 post. full post @ my blog :&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;http://imthezuk.blogspot.com/&quot;&gt;&lt;b&gt;http://imthezuk.blogspot.com/&lt;/b&gt;&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
</description>
                    </item>
                <item>
            <title>My new security blog</title>
                            <pubDate>Fri, 04 Dec 2009 04:07:36 -0600</pubDate>
                                        <link>https://www.openrce.org/blog/view/1524/My_new_security_blog</link>
                                        <author>DelightedZuk &lt;email-suppressed@example.com&gt;</author>
                                                    <description>http://imthezuk.blogspot.com/&lt;br /&gt;
cheers :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
BTW, are there any more guys here @ SANS London event now??</description>
                    </item>
                <item>
            <title>Python POST command</title>
                            <pubDate>Thu, 10 Sep 2009 03:32:30 -0500</pubDate>
                                        <link>https://www.openrce.org/blog/view/1497/Python_POST_command</link>
                                        <author>DelightedZuk &lt;email-suppressed@example.com&gt;</author>
                                                    <description>I've built a project for the company I work in, we'll publish it later, but one of the problems of the project was using another proxy which didn't implemented a POST method (and now I know why, it was hell to find about it).&lt;br /&gt;
So, I will make your life easier, in-order to get a POST parameters, there's socket fileobject called rfile, that's what you're looking for.&lt;br /&gt;
Params = self.rfile.read(int(rinstance.headers[&amp;quot;content-length&amp;quot;]))&lt;br /&gt;
After that, building a POST (ssl or not) request using raw data is relatively easy.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I hope it will save you a few minutes,&lt;br /&gt;
Cheers.&lt;br /&gt;
&lt;br /&gt;
</description>
                    </item>
            </channel>
</rss>
