Endpoint

4/16/2015
05:00 PM
Connect Directly
Twitter
Twitter
RSS
E-Mail

7 Deadly Sins That Get Users Hacked

How users and their endpoints are leveraged by the bad guys to eventually find their way to critical data
1 of 8

Image: (Pixabay)
Image: (Pixabay)

1 of 8
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
pawan14
50%
50%
pawan14,
User Rank: Apprentice
6/8/2015 | 4:21:42 AM
Re: Username/password is main problem
The long we continue to user Username/password combination the worse these situation will get. 
SashKhe
50%
50%
SashKhe,
User Rank: Apprentice
4/23/2015 | 7:27:30 AM
Re: Username/password is main problem
If people would start using key-patterns instead of letter patterns as password, that would help too.
Example, "draw" a circle on your keyboard, every second key pressed is with shift - you just made a strong password that's as easy to remember as looking at your keyboard.
SashKhe
50%
50%
SashKhe,
User Rank: Apprentice
4/23/2015 | 7:24:54 AM
Re: Username/password is main problem
Don't forget the salt.
MarkSitkowski
50%
50%
MarkSitkowski,
User Rank: Moderator
4/20/2015 | 11:40:45 PM
Re: Username/password is main problem
I agree - and so do thousands of others, probably.

Thing is, it's not even necessary to send anything meaningful. Imagine, that you have a secret word, which only you know. Now imagine you are presented with an alphabet, under which is a random array of 0's and 1's. You enter the pattern corresponding to your secret word, which won't be the same next time you login, as the 0's and 1's are random.

Oh, yes, just in case anyone is listening on the network, you don't send the solution, you just send its SHA256 hash.

Isn't that better than passwords?
cyclepro
50%
50%
cyclepro,
User Rank: Strategist
4/20/2015 | 9:07:04 AM
hacking
One other way that was not mentioned is through Instant Messaging.

 

I always just delete any messages where I do not recognize the person.

 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/18/2015 | 11:11:24 AM
Re: Fake phone calls
Nice tactic. You can also tell them what a good service they acre providing and you want to send kudos to their bosses if they can provide phone number for that. You never know, they may be providing real number of their boss.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/18/2015 | 11:07:50 AM
Re: Fake phone calls
I tend to do the same thing, not answering any unknown and waiting for voice message for the number I do not recognize. It is safer and saving time that way.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/18/2015 | 11:05:40 AM
Re: Fake phone calls
I like the idea, keeping them on the line until they hang up. Or giving the all the fake information so they can continue their effort.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/18/2015 | 11:02:35 AM
Username/password is main problem
The long we continue to user Username/password combination the worse these situation will get. Today, most common attacks are phishing and social engineering attacks on the end-users side, even these attacks are the results of the fact tags we use username/password combination. We need to find out a way to get rid of it or move the next level such as two or three factor authentication.
SmarterThanTheAverageBear
50%
50%
SmarterThanTheAverageBear,
User Rank: Apprentice
4/17/2015 | 7:55:31 PM
Re: Fake phone calls
Tell them your boss wants to hear more about their services and you are going to forward their call to him then forward them to the FBI/NSA or one of the otgher alphabet soups :)
Page 1 / 2   >   >>
What We Talk About When We Talk About Risk
Jack Jones, Chairman, FAIR Institute,  7/11/2018
Ticketmaster Breach Part of Massive Payment Card Hacking Campaign
Jai Vijayan, Freelance writer,  7/10/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14084
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for MKCB, an Ethereum token. If the owner sets the value of sellPrice to a large number in setPrices() then the "amount * sellPrice" will cause an integer overflow in sell().
CVE-2018-14085
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for UserWallet 0x0a7bca9FB7AfF26c6ED8029BB6f0F5D291587c42, an Ethereum token. First, suppose that the owner adds the evil contract address to his sweepers. The evil contract looks like this: contract Exploit { uint public start; function swe...
CVE-2018-14086
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for SingaporeCoinOrigin (SCO), an Ethereum token. The contract has an integer overflow. If the owner sets the value of sellPrice to a large number in setPrices() then the "amount * sellPrice" will cause an integer overflow in sell(...
CVE-2018-14087
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for EUC (EUC), an Ethereum token. The contract has an integer overflow. If the owner sets the value of buyPrice to a large number in setPrices() then the "msg.value * buyPrice" will cause an integer overflow in the fallback functio...
CVE-2018-14088
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for STeX White List (STE(WL)), an Ethereum token. The contract has an integer overflow. If the owner sets the value of amount to a large number then the "amount * 1000000000000000" will cause an integer overflow in withdrawToFounde...