Bitcoin Forum
May 02, 2024, 12:08:40 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Serious Security glitch in Electrum !!  (Read 499 times)
apoorvlathey (OP)
Hero Member
*****
Offline Offline

Activity: 1162
Merit: 547


CryptoTalk.Org - Get Paid for every Post!


View Profile WWW
October 27, 2016, 03:36:22 PM
 #1

I have noticed a very serious security breach in electrum desktop wallet. I have set a password to secure my wallet, but it is of no use.
While adding new address, it asked for a password, i pressed cancel even then new window to enter the private key appeared and i was able to add new bitcoin address without the password !
I then tried to sign a message with the new address added to the wallet. It asked me for the password, i again pressed cancel, and to my surprise the sign/verify window still appeared and i could successfully sign message with that address without even entering the password.
I have not tried this with a bitcoin transaction though.

1714608520
Hero Member
*
Offline Offline

Posts: 1714608520

View Profile Personal Message (Offline)

Ignore
1714608520
Reply with quote  #2

1714608520
Report to moderator
"This isn't the kind of software where we can leave so many unresolved bugs that we need a tracker for them." -- Satoshi
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
btchris
Hero Member
*****
Offline Offline

Activity: 672
Merit: 504

a.k.a. gurnec on GitHub


View Profile WWW
October 27, 2016, 05:18:32 PM
 #2

It doesn't look like this was a known bug, but it was fixed here (as a result of fixing a related issue) in version 2.7.10 (current version is 2.7.11).

After upgrading, you'll still need to fix your wallet. Delete any affected addresses on the addresses tab, and import them again.
HI-TEC99
Legendary
*
Offline Offline

Activity: 2772
Merit: 2846



View Profile
October 27, 2016, 07:57:07 PM
 #3

I have noticed a very serious security breach in electrum desktop wallet. I have set a password to secure my wallet, but it is of no use.
While adding new address, it asked for a password, i pressed cancel even then new window to enter the private key appeared and i was able to add new bitcoin address without the password !
I then tried to sign a message with the new address added to the wallet. It asked me for the password, i again pressed cancel, and to my surprise the sign/verify window still appeared and i could successfully sign message with that address without even entering the password.
I have not tried this with a bitcoin transaction though.

By "adding new address" do you mean you created a new wallet and left the password blank when it asked you to create one? The dialog box says "enter nothing if you want to disable encryption".




That's not a bug, it's a feature. If you don't want to be forced into entering a password every time you send Bitcoins then you miss out the password when you create the wallet.

I can't find an option in the GUI to add a new address, I think you can only do that in the console through the command line.
btchris
Hero Member
*****
Offline Offline

Activity: 672
Merit: 504

a.k.a. gurnec on GitHub


View Profile WWW
October 27, 2016, 09:42:07 PM
Last edit: October 27, 2016, 10:41:49 PM by btchris
 #4

I can't find an option in the GUI to add a new address, I think you can only do that in the console through the command line.

You misunderstood OP's issue.

You can create a wallet containing loose (non-HD) keys: create a "standard" wallet, select "Use public or private keys", and paste in one or more keys. Set a password when asked.

After creating the wallet, go to Wallet --> Private keys --> Import to import additional keys. Electrum will ask you for your password. In versions 2.7.9 and earlier, you could hit Cancel on the password prompt, but Electrum would still allow you to enter new private keys for import, and you'd end up with a wallet with the original keys encrypted, but the new keys in plaintext.

As I said above, this was fixed in 2.7.10.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!