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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20040106203400.435f4d1c.backblue@netcabo.pt>
From: backblue at netcabo.pt (backblue)
Subject: Re: Linux kernel do_mremap() proof-of-concept
 exploit code

On Tue, 6 Jan 2004 11:47:26 -0700
"Epic" <epic@...k3r.com> wrote:

> I too tested it on my 2.4.23 kernel with grsec, and nothing.
> 
> 
> ----- Original Message ----- 
> From: "Daniel Husand" <io@...v.us>
> To: <full-disclosure@...ts.netsys.com>
> Sent: Tuesday, January 06, 2004 10:54 AM
> Subject: [Full-Disclosure] Re: Linux kernel do_mremap() proof-of-concept
> exploit code
> 
> 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Christophe Devine wrote:
> >
> > | The following program can be used to test if a x86 Linux system
> > | is vulnerable to the do_mremap() exploit; use at your own risk.
> > |
> > | $ cat mremap_poc.c
> > |
> >
> > This didnt do anything on my 2.4.23-grsec kernel.
> >
> > - --
> > Daniel
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.2.3 (MingW32)
> > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> >
> > iD8DBQE/+vZz1PIgHh6MkiIRAiqNAKCiuyxtA9rgaAS+eT3o9ATvLE7EuQCeJAZP
> > Xf8JIDehgtGba4b1Eb2Qv0w=
> > =xyYM
> > -----END PGP SIGNATURE-----
> >
> > _______________________________________________
> > Full-Disclosure - We believe in it.
> > Charter: http://lists.netsys.com/full-disclosure-charter.html
> 
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html
Offcourse not! that exploit was not made for kernels with grsec and another kernel with patch's similar to that one! but it is vuln anyway, just code you the exploit for the grsec kernel!
you have to pass a coulple of things over...


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ