NordVPN Linux does not enforce 2FA even it's enabled in user settings
After installation there the Linux NordVPN does not EVER verify the 2FA code. This is what happens:
--- snip ---
memyself@mylinux ~> sudo su
root@mylinux:/home/homeuser# nordvpn status
Status: Disconnected
root@mylinux:/home/homeuser# nordvpn login
Please enter your login details.
Email: [email protected]
Password: *******
Welcome to NordVPN!
You can now connect to VPN by using 'nordvpn connect'.
root@mylinux:/home/homeuser# nordvpn connect France
Connecting to France #742 (fr742.nordvpn.com)
You are connected to France #742 (fr742.nordvpn.com)!
root@mylinux:/home/homeuser#
--- snip ---
That log is from Linux Mint 20.2 with all the latest patches, kernel and latest version of NordVPN Linux (3.10.0) (normal apt upgrade process done for everything). Username, hostname etc. have been just modified for privacy purposes.
Also note note, this happened on the first run on that Linux computer so 2FA should've been enforced. But at in any point does the NordVPN client call for 2FA token. :(
Now, a honest question:
Who does not see this as a potential security hole here? It's the NordVPN server who should ensure that not ANY client can log in without correct 2FA token if it's enabled. Now a Linux client can any time login if correct credentials are known.
It seems that the the 2FA is implemented on the client side completely. Which is not the correct way to do it. Fake spoofing NordVPN clients start to arrive which can bypass 2FA on any account.
Windows and Mobile NordVPN clients seem to enforce it, but if the 2FA verification is done on client side then the whole meaning is nullified.
Btw, this happened when I posted the above msg in r/nordvpn
FeedbackSorry, this post has been removed by the moderators of r/nordvpn.Moderators remove posts from feeds for a variety of reasons, including keeping communities safe, civil, and true to their purpose.
Mopping a serious problem under the carpet?
I’m also a NordVPN customer, and not only I do not use 2FA, I deliberately use easy to guess, previously compromised passwords. I’ve also handed out those credentials to plenty of my friends.
Just in case they happen to log the network activity of their users, what this can achieve is plausible deniability and noise. Lots of noise.
For comparison, mullvad accounts have no separate identification and authentication. Each account is a 16 digit number, and knowledge of that number allows you to administer the entire account. Usernames and passwords don't exist
Yeah this was a huge learning curve for me. When you use a Mullvad OpenVPN config file, the username is your account number, and the password is the account number too.
All a bad actor has to do is enumerate account numbers programmatically and they could potentially own hundreds of accounts, although generating those would be difficult and a lot of it relies on chance.
They're probably not mopping the issue under the carpet, but rather reddit is not their bug reporting platform.
Though the page does say account takeover is out of scope, so I'm unsure what the program is even for.
[1] https://hackerone.com/nordsecurity
The client keeps on failing to request the list of available serves because of some strange networking bug.