Windows Password Clues Easy To Crack

Metasploit penetration testing framework has been updated with an attack that retrieves all Windows 7 and 8 password clues.

11 Security Sights Seen Only At Black Hat

(click image for larger view and for slideshow)

User-provided password retrieval hints in Windows 7 and 8 operating systems are vulnerable to being retrieved and decoded by attackers.

That finding was made by two security researchers who've been studying ways to increase the reliability of tools designed to extract Windows registry information.

"In the process of going through one of our test cases on a Windows 8 machine on Saturday, we stumbled across a new key ('UserPasswordHint') that we had not seen before in the SAM database," said vulnerability researcher Jonathan Claudius, who works for Trustwave's SpiderLabs research team, in a blog post. Claudius's co-researcher is Ryan Reynolds, who's in charge of penetration testing services for public accounting and consulting firm Crowe Horwath. "To both of us, this seemed like a rather odd, but intriguing, key that would be cool to explore a bit more 'at some point,'" Claudius said.

The research didn't sit for long. "Being the impatient weirdo that I am," Claudius said, he dove in and soon worked out "how to how to extract/decode User Password Hints from the Windows registry." By Tuesday, he'd also updated the "hashdump" module included in the open source Metasploit penetration testing toolkit, enabling it to grab user password hints from Windows 7 and 8 systems. "This seems like it would be very helpful for penetration testers by giving them more insight into what the user's password might be," he said.

The finding builds on the researchers' recent success at overcoming recurring hash corruption problems experienced by registry extraction tools such as Metasploit, Cain and Able, Pwdump, Fgdump, L0phtcrack, Samdump, Creddump, Pwdump5, and Pwdump7. The pair detailed their findings at last month's Black Hat and DEFCON information security conferences in Las Vegas, and said they've been working with the relevant developers to create patches.

So how might Microsoft fix the Windows registry to block user-password-retrieval-hint attacks? Responding to a question posted on a discussion forum, Claudius doesn't necessarily think this information needs to be encrypted, but he didn't provide any specific mitigation strategies.

A Microsoft spokeswoman didn't immediately respond to a request for comment on the vulnerability identified by Claudius and Reynolds, or on potential strategies Windows users could employ to mitigate related attacks.

Claudius did note that the password hints could already have been retrieved using other attack techniques, although not necessarily en masse. "Anyone who has physical access can guess a username and obtain the associated hint on a one-by-one basis," he said. "The focus of my additions [was] to obtain this information remotely as part of a post-exploitation process and steal all the hints on the system."

One of the biggest challenges facing IT today is risk assessment. Risk measurement and impact assessment aren't exact sciences, but there are tools, processes, and principles that can be leveraged to ensure that organizations are well-protected and that senior management is well-informed. In our Measuring Risk: A Security Pro's Guide report, we recommend tools for evaluating security risks and provide some ideas for effectively putting the resulting data into business context. (Free registration required.)

A few days ago, I had met the headache things that I had forgotten Windows login password. Fortunately I got to know the PCUnlocker program, which helped me reset Windows password instantly yet no data loss.

So, users out there should be warned - putting your password in clear text in the password hint field is probably a worse idea now than it was two weeks ago.

Password security will always come down to the user, period. If a user does not know how to secure their account properly, via password or other means, their account (and their system, in most instances) will not be safe.

If it weren't for users, secure systems would be easy to create and maintain.

Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.

Published: 2017-05-09NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

Published: 2017-05-08unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

Published: 2017-05-08Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

Published: 2017-05-08Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.