lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <185397.73792.qm@web122401.mail.ne1.yahoo.com> Date: Thu, 23 Jun 2011 02:53:21 -0700 (PDT) From: Kevin Johnson <kevjohnson71@...oo.com> To: full-disclosure@...ts.grok.org.uk Subject: From kernel memory disclosure to privilege escalation: when and how? Hello! Could somebody write what threats there are when kernel memory disclosure is found? I mean not along with another bug (since kmem disclosure could lead to some interesting pointers addresses and values, etc), but only itself!? I guess it could lead to /etc/shadow disclosure, if some suid programs accessing it would be running in the background (chsh, for example). Is it correct? BTW, when chsh and other programs-accessing-shadow-file are running, where do they store the /etc/shadow content? On the kernel stack in it's thread_union, or somewhere else? So, besides /etc/shadow disclosure, are there any significant places, where kernel memory disclosure could lead to very likely privilege escalation? Thank you. _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
Powered by blists - more mailing lists