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
7 Ways To Charm Users Out of Their Passwords
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
JulietteRizkallah
100%
0%
JulietteRizkallah,
User Rank: Ninja
7/28/2016 | 11:43:51 AM
Re: Wow...
Well, i hope you use unique password because many times hackers will test the password they obtain - by theft, bribe or money - against many other systems until they get into the one they want access to.  You may think you can just chnage your password as soon as revealed and all is safe but hackers are not that stupid, they usually do not ask for the password of the system they wnat access to, they want to study your passwords, test them against other corporate systems until they get their way in.  And be worried, there is always one app you forget that will let them in!
T Sweeney
100%
0%
T Sweeney,
User Rank: Moderator
7/28/2016 | 10:21:40 AM
Re: Wow...
Ha! Thanks, Whoopty... that's a better title, actually: 7 Ways to Bribe Users! I'll admit I was surprised at how many ways there were to get users to give up the goods. Some little treat is actually a great conversational opener for a social engineer, provided they're willing to try it in person and forego the anonymity of the phone.

The other surprise: How many users will give up their passwords just by being asked... no incentive required. What's up with that?
Whoopty
100%
0%
Whoopty,
User Rank: Ninja
7/28/2016 | 8:02:00 AM
Wow...
I thought this piece would be about legitimate social engineering techniques, not outright bribery of people! I'm shocked so many would give up information for a pen.

A cookie I can understand but still...

I might be tempted by the cash, but only because I would immediately change my password after they gave it to me. 
<<   <   Page 2 / 2


News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-23381
PUBLISHED: 2021-04-18
This affects all versions of package killing. If attacker-controlled user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23374
PUBLISHED: 2021-04-18
This affects all versions of package ps-visitor. If attacker-controlled user input is given to the kill function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23375
PUBLISHED: 2021-04-18
This affects all versions of package psnode. If attacker-controlled user input is given to the kill function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23376
PUBLISHED: 2021-04-18
This affects all versions of package ffmpegdotjs. If attacker-controlled user input is given to the trimvideo function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23377
PUBLISHED: 2021-04-18
This affects all versions of package onion-oled-js. If attacker-controlled user input is given to the scroll function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.