Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
Password Manager LastPass Hacked
Oldest First  |  Newest First  |  Threaded View
Markus5
100%
0%
Markus5,
User Rank: Strategist
6/16/2015 | 2:31:48 PM
Offline approach
Because of these breaches I use offline approach to my password management and use Sticky Password with their WiFi only syncing and that works pretty great for me. I don't wanna expose myself to the cloud world with all my passwords in one basket.
RyanSepe
100%
0%
RyanSepe,
User Rank: Ninja
6/16/2015 | 3:18:20 PM
Re: Offline approach
The offline approach is definitely the way to go in my opinion and if you are managing a password vault for an enterprise than offline internal would be the most precise so that there isn't a single point of failure. I am always wary of storing passwords in the cloud. Specifically, because there is more exposure due to the its publicly facing mandate.
alabrian
50%
50%
alabrian,
User Rank: Apprentice
6/17/2015 | 12:22:15 PM
Re: Offline approach
Imo, the catch-all favorite reply to all things infosec "it depends on the use case" applies here as well. Offline password management surely eliminates certain risks, but is exposed more to others, so it all depends on personal preference and how one assesses those risks.

For instance, how easily can those devices be stolen? Are there backups of that password database and how are they geographically dispersed? How are the backups being kept in sync? 

To give one of many examples, I might be content in knowing that I keep everything offline and thus avoid all kinds of risk involved with online threats, but the risk of being susceptible to natural disasters increases.

It is very easy to imagine a scenario where people had a nasty surprise waiting for them when realizing that their copies of their password database they kept in USB drives was outdated after losing their desktop PC + NAS due to an earthquake.

Having those hashes + salts stolen just means you have a certain amount of time to change your master password until you are safe again. And that's before factoring in two-factor authentication, which further reduces that risk.

 

 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/17/2015 | 12:39:19 PM
Not surprised at all
Why would anybody think that when there is a password repository somewhere hackers would not find a way to hack it? That is like a perfect target to spend time on it.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/17/2015 | 12:43:07 PM
Re: Offline approach
Agree, all the passwords in one basket is not realty great idea at all. Although the announcement points out those passwords are not compromised, this does not mean they are not going to be.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/17/2015 | 12:45:03 PM
Re: Offline approach
Agree, all the passwords in one basket is not realty great idea at all. Although the announcement points out those passwords are not compromised, this does not mean they are not going to be.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/17/2015 | 12:50:17 PM
Re: Offline approach
Agree. This confirms one of my previous points. We can keep it offline but we are not removing the risk of being hacked. Your kids may expose your flash drives or HDs that you keep those passwords without you knowing it. Ultimate solution is actually getting rid of password requirements in our lives and defining new ways for authentication and authorization.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
6/17/2015 | 3:37:21 PM
Re: Offline approach
Yes agreed there is always a use case. What about, for an internal configuration, putting the password vault on a server. This server has no outside internet access and on the endpoints you have to authenticate using your network login. If you lose the device the passwords are not stored locally and you can't connect to the domain off network, with exceptions of course. The backups are managed at the server level to stay consistent with other backup methodologies. I think this is a similar method that I would want to pursue.

Lets posit inherent flaws with the above configuration. It'll help to derive issues so that solutions could be pondered.


Commentary
How SolarWinds Busted Up Our Assumptions About Code Signing
Dr. Jethro Beekman, Technical Director,  3/3/2021
News
'ObliqueRAT' Now Hides Behind Images on Compromised Websites
Jai Vijayan, Contributing Writer,  3/2/2021
News
Attackers Turn Struggling Software Projects Into Trojan Horses
Robert Lemos, Contributing Writer,  2/26/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: George has not accepted that the technology age has come to an end.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2009-20001
PUBLISHED: 2021-03-07
An issue was discovered in MantisBT before 2.24.5. It associates a unique cookie string with each user. This string is not reset upon logout (i.e., the user session is still considered valid and active), allowing an attacker who somehow gained access to a user's cookie to login as them.
CVE-2020-28466
PUBLISHED: 2021-03-07
This affects all versions of package github.com/nats-io/nats-server/server. Untrusted accounts are able to crash the server using configs that represent a service export/import cycles. Disclaimer from the maintainers: Running a NATS service which is exposed to untrusted users presents a heightened r...
CVE-2021-27364
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. drivers/scsi/scsi_transport_iscsi.c is adversely affected by the ability of an unprivileged user to craft Netlink messages.
CVE-2021-27365
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. Certain iSCSI data structures do not have appropriate length constraints or checks, and can exceed the PAGE_SIZE value. An unprivileged user can send a Netlink message that is associated with iSCSI, and has a length up to the maximum length...
CVE-2021-27363
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. A kernel pointer leak can be used to determine the address of the iscsi_transport structure. When an iSCSI transport is registered with the iSCSI subsystem, the transport's handle is available to unprivileged users via the sysfs file system...