| 1 |
I failed to crash any of my test systems with that exploit, hardened or |
| 2 |
not. And no-one else seems to have confirmed that it does work. |
| 3 |
I can however crash x86_64 systems with another unfixed bug (up to |
| 4 |
2.6.12-rc4). |
| 5 |
|
| 6 |
Antoine |
| 7 |
|
| 8 |
On Fri, 2005-05-13 at 15:09 +0100, Pedro Venda wrote: |
| 9 |
> hi everyone, |
| 10 |
> |
| 11 |
> Has anyone got a clue on how should the proof of concept code behave on |
| 12 |
> vulnerable and not vulnerable machines? |
| 13 |
> |
| 14 |
> On a PaX+grsecurity hardened server, it outputs: |
| 15 |
> |
| 16 |
> [+] ./elfcd1 argv_start=0xb47b23d4 argv_end=0xb47b23dc ESP: 0xb47b1890 |
| 17 |
> [+] phase 1 |
| 18 |
> [+] AAAA argv_start=0xb5e0442e argv_end=0xb5e04432 ESP: 0xb5e03930 |
| 19 |
> [+] phase2, <RET> to crash Killed |
| 20 |
> |
| 21 |
> and doesn't core-dump. Also it doesn't warn about the segmentation violation |
| 22 |
> process in the logs... |
| 23 |
> |
| 24 |
> On my laptop, a test server and 2 other workstations (standard 2.6.11.5-8 |
| 25 |
> kernels) results are consistent but different from the hardened server: |
| 26 |
> pjlv@archon test $ ./elfcd1 |
| 27 |
> |
| 28 |
> [+] ./elfcd1 argv_start=0xbfffeff7 argv_end=0xbfffefff ESP: 0xbfffedb0 |
| 29 |
> [+] phase 1 |
| 30 |
> [+] AAAA argv_start=0xbfff6fee argv_end=0xbfff6ff2 ESP: 0xbfff6e80 |
| 31 |
> [+] phase 2, <RET> to crash Segmentation fault (core dumped) |
| 32 |
> |
| 33 |
> and core-dumps. |
| 34 |
> |
| 35 |
> any help? is the hardened server secure? I suppose so, since it didn't core |
| 36 |
> dump. |
| 37 |
> |
| 38 |
> regards, |
| 39 |
> pedro venda. |
| 40 |
|
| 41 |
-- |
| 42 |
gentoo-security@g.o mailing list |
| 43 |
|
| 44 |
-- |
| 45 |
gentoo-hardened@g.o mailing list |
Archives