From: Gavin Andresen <gavinandresen@gmail•com>
To: Doug Huff <dhuff@jrbobdobbs•org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>,
full-disclosure@lists•grok.org.uk
Subject: Re: [Bitcoin-development] Bitcoin fun day!
Date: Sun, 19 Jun 2011 18:33:14 -0400 [thread overview]
Message-ID: <BANLkTikiBz52hVreTVJM4Q15rtfGLVE2sQ@mail.gmail.com> (raw)
In-Reply-To: <2B2201C1-E59F-47D4-BF67-08FDB0DDE386@jrbobdobbs.org>
Some of us take private disclosures of vulnerabilities very seriously.
In any case, the ClearCoin CSRF vulnerability is fixed. Thank you for
bringing it to my attention.
On Sun, Jun 19, 2011 at 5:54 PM, Doug Huff <dhuff@jrbobdobbs•org> wrote:
> In light of this decision I would like to report multiple CSRF vulnerabilities in http://clearcoin.appspot.com .
>
> This set of CSRFs are particularly nasty since this is hosted on appspot and uses google account auth. So long as you stay logged into your google account you are vulnerable to this CSRF.
--
--
Gavin Andresen
http://clearcoin.com/
next prev parent reply other threads:[~2011-06-19 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-19 21:54 Doug Huff
2011-06-19 22:33 ` Gavin Andresen [this message]
2011-06-19 22:36 ` Douglas Huff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTikiBz52hVreTVJM4Q15rtfGLVE2sQ@mail.gmail.com \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=dhuff@jrbobdobbs$(echo .)org \
--cc=full-disclosure@lists$(echo .)grok.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox