Groklaw - Digging for Truth

	When you want to know more...

Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines

ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

You won't find me on Facebook

Donate

No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.

What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments

Sponsors

Hosting:

On servers donated to ibiblio by AMD.

Webmaster

The attack will always work | 128 comments | Create New Account

Comments belong to whoever posts them. Please notify us of inappropriate comments.

The attack will always work

Authored by: Anonymous on Saturday, January 26 2013 @ 12:34 AM EST

That's only true if malloc allocates memory sequentially.
This is true for mallocs based on rbrk/sbrk. There are
other ways to implement malloc. Some of the other ways will
randomize where the blocks come from. So even though memory
is full, it doesn't mean you know where the last few blocks
came from.

If you have access to the pointers returned by malloc, then
yes, you can always make this attack work. But the point of
this exploit is that you are able to make it work from
javascript without access to the actual values returned by
malloc.

If you have access to the pointers and can call free, I
suspect you can call exec or anything else you want.
Although I suppose sandbox developers should take note.
malloc/free is not necessarily safe if you can load
unsandboxed dll's.

[ Reply to This | Parent | # ]

The attack will always work - Authored by: Anonymous on Saturday, January 26 2013 @ 11:11 AM EST
- The attack still needs refinement - Authored by: SpaceLifeForm on Saturday, January 26 2013 @ 02:36 PM EST

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )