full-disclosure - Re: POC for a simple gmail/possible code injection into html wich can be executed in an email, i will make the PoC code and explain how here and now...

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: <BANLkTik0aiN-QhsxiGDHQ9+BKnNEU_aHog@mail.gmail.com>
Date: Sat, 11 Jun 2011 19:45:29 -0500
From: adam <adam@...sy.net>
To: noloader@...il.com
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: POC for a simple gmail/possible code
 injection into html wich can be executed in an email,
 i will make the PoC code and explain how here and now...

Somehow, I seriously doubt that.

The point is, broken English or not - this has to be the most laughable PoC
I've ever seen. He originally insists that this is a problem related to (web
based?) mail providers (which would lead anyone to believe is server
related) and then turns around and begins referencing external libraries
(that he can't even name?).

Lastly, before diving face first into his ass - you should have probably
performed a Google search. I'll give you a hint, he's not located in some
third world country.

On Sat, Jun 11, 2011 at 7:30 PM, Jeffrey Walton <noloader@...il.com> wrote:

> On Sat, Jun 11, 2011 at 8:13 PM, adam <adam@...sy.net> wrote:
> > When the English version becomes available, please let me know.
> I'd bet secn3t's english is better than your speaking his native tongue....
>
> > On Sat, Jun 11, 2011 at 7:02 PM, -= Glowing Doom =- <secn3t@...il.com>
> > wrote:
> >>
> >> Systems wich appear vulnerable: EVERY single one i have tried...
> >>
> >> How:
> >>
> >> I wrote that sentecne, then, i backspaced it and blacked it over with
> copy
> >> , then, enter url to wherver i want...
> >> There is 3 ways i have found todo this, when i dissected one of them,
> the
> >> URL/Sentence, was gfull of x41\x41\x41 , very strange... because it is
> still
> >> able to be done 3 ways, and the simplest way does NOT require even html
> >> 'link' to section, wich is what MST be done, altho on older emailer
> systems,
> >> I see that it is simple as backspace over the sentence,then type the
> url, it
> >> a'appears' at first , to be a normal deleted sentence, but when I open
> and
> >> dissect, it shows URL/41/41/41 then all over the email page, same thing
> ...
> >> I know this might be confusing,  I traced the problem to a dll or lib
> wich
> >> is for text editing , and that dll is a VERY common one on any system,
> sofar
> >> not one mailing system, has NOT had this vuln... yet, i have seen
> another
> >> 'version' of this attack type, but, they can ONLY spoof a URL... This
> one,
> >> you can make the whole email, a url... i will do this right now..
> >>
> >> [SNIP]
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>

Content of type "text/html" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/