This instructable has been removed by the author.
105
comments
|
Add Comment
|
| 1-50 of 105 | next » |
visit this site http://xt-hackgold.com
recomended
Speedy toys sells airsoft weapons and are exploitable.
I am looking for a clothing or knife store that is exploitable.
Best regards yx516
I'm going to leave this one up because I feel the best way to close security flaws is to expose them to daylight. This reminds me of the Security Analysis of the Diebold AccuVote-TS Voting Machine. While this Instructable clearly isn't as well written as the Princeton paper, and the intent seems to be more on the negative than the positive side, it still exposes a flaw and encourages PayPal to fix it.
Tamper Data seems to be an interesting extension. I wonder what other things it can do?
I respectfully disagree, and here's why:
1) In a typical "white hat" hacking scenario, it's considered good form to approach the vendor with any security issues before releasing significant details to the public. Releasing details of an exploit to the public (or threatening to) is usually the measure of last resort used to strong-arm vendors who refuse to issue fixes. In the case of the Princeton paper there has been an ongoing denial on the part of Diebold that security flaws exist. Was PayPal even given a chance to respond to this alleged security flaw?
2) The authors of the Princeton paper withheld key details that would be needed to actually exploit the vulnerabilities they describe. This write-up does not show similar restraint. In fact, it seems to be nothing but a description of how to exploit the vulnerability. There is really no security analysis to speak of.
Also, from vicarious experience, I can tell you that revealing security exploits can be more trouble than it's worth. If you have to hire an attorney to respond to legal threats (even if those threats are totally bogus), it's going to cost you several hundred dollars an hour. In the case of the Princeton paper they reveal security flaws that may undermine a core element of our electoral process. In this case you're revealing a security flaw that lets people steal things. Honestly, if it were me, that's not something I'd be willing to go to bat for.
I'll admit that the Princeton paper was a bit of a stretch. Perhaps the U-lock pen hack would have been a better example. In any case, I did mean remind rather than "is directly analogous to".
I agree with your first point. However, it's the author's choice to publish it, and considering the author seems to be silent on this issue so far, we can only make assumptions. I will admit that the tone of the Instructable indicates a pretty clear answer. Since this was published and presumably there are already copies of it across the internet, whether PayPal was contacted is water under the bridge for the question of whether I should leave it published.
Your second point directly addresses whether I should leave it or not. I made my decision based on two thoughts: Potential damage and credibility.
The level of potential damage from this hack seems low. No one's life is in danger, there's a substantial paper trail left when someone does this so it's easy to find the culprits, and PayPal's reputation hinges on their system being robust to these types of attacks. I bet PayPal will refund the full amount that anyone loses to this.
If the author had posted an Instructable saying "I can steal from PayPal" but didn't give details no one would believe it and I would have unpublished the Instructable for lack of instruction. I'm going out on the limb here, but it's my guess that if the author had sent these instructions to PayPal's customer support, they would have been lost in multiple layers of management and not acted on in a timely fashion. Sadly, that experiment can't be run this time round.
So, that brings me to the point. When an individual finds a security hole, and he doesn't have the credibility to directly affect the holder of that security nor the credibility to publish without complete instructions and be believed, what options does he have?
I don't know the answer, and obviously I'm experimenting here with what the Instructables community finds acceptable. I continue to think this a great test case for these questions, though - no has to use PayPal, the potential damage is low, and no lives are at stake.
Imagine what this debate would be like if we were talking about "hack the Golden Gate to fall down." I'm gonna go add that phrase to our Instructable-spam-filter right now, just in case.
| 1-50 of 105 | next » |
![]() |







































