Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BitLocker under the latest github repo does not break a wordlist attack #3997

Open
MrX0r opened this issue May 6, 2024 · 5 comments
Open
Labels

Comments

@MrX0r
Copy link

MrX0r commented May 6, 2024

Hello, an error has crept into the new repo of v6.2.6-851-g6716447df.

BitLocker (22100) with wordlist attack does not work, the brute force function works fine.

Under the last stable Hashcat version v6.2.6 from 2022.09.02 the Wordlist attack for Windows works.

@MrX0r MrX0r added the bug label May 6, 2024
@ventaquil
Copy link
Contributor

Can you provide hash string and password? Are you using CUDA or OpenCL?

I created simple wordlist and works like a charm.

hashcat (v6.2.6-851-g6716447df) starting

OpenCL API (OpenCL 2.0 AMD-APP (3305.0)) - Platform #1 [Advanced Micro Devices, Inc.]
=====================================================================================
* Device #1: Vega 10 XL/XT [Radeon RX Vega 56/64], 8064/8176 MB (6949 MB allocatable), 64MCU
* Device #2: Vega 10 XL/XT [Radeon RX Vega 56/64], 8064/8176 MB (6949 MB allocatable), 64MCU
* Device #3: Vega 10 XL/XT [Radeon RX Vega 56/64], 8064/8176 MB (6949 MB allocatable), 64MCU
* Device #4: Vega 10 XL/XT [Radeon RX Vega 56/64], 8064/8176 MB (6949 MB allocatable), 64MCU

Minimum password length supported by kernel: 4
Maximum password length supported by kernel: 256

Hashes: 2 digests; 2 unique digests, 2 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1

Optimizers applied:
* Slow-Hash-SIMD-LOOP

Watchdog: Temperature abort trigger set to 90c

Host memory required for this attack: 1124 MB

Dictionary cache hit:
* Filename..: dictionary.txt
* Passwords.: 44392
* Bytes.....: 358349
* Keyspace..: 44392

Cracking performance lower than expected?

* Append -w 3 to the commandline.
  This can cause your screen to lag.

* Append -S to the commandline.
  This has a drastic speed impact but can be better for specific attacks.
  Typical scenarios are a small wordlist but a large ruleset.

* Update your backend API runtime / driver the right way:
  https://hashcat.net/faq/wrongdriver

* Create more work items to make use of your parallelization power:
  https://hashcat.net/faq/morework

$bitlocker$0$16$3cf222a4ba5bc6392173393556e81c02$1048576$12$c0ddf6f0fa3cd70103000000$60$684233ee95afa074d3bc0b4531579dd6d74e328b538809c74146994ed88dfce0976e6259579bc23456417c2216fec26eac760b044dd8753f6b65f94f:@1B2c3d4
$bitlocker$0$16$cf349b321604bc965a358db438217396$1048576$12$40ca1150fb3cd70103000000$60$10ae0120ae4dc52082eefbb6e58ac8b1010acf192bcea7afef637d7d4e25e2c4cc201e2452fc343823cc915d6e2b0e78b9a87d51c57421792d89ccde:@1B2c3d4

Session..........: hashcat
Status...........: Cracked
Hash.Mode........: 22100 (BitLocker)
Hash.Target......: bitlocker.txt
Time.Started.....: Mon May  6 13:29:27 2024 (10 mins, 16 secs)
Time.Estimated...: Mon May  6 13:39:43 2024 (0 secs)
Kernel.Feature...: Pure Kernel
Guess.Base.......: File (dictionary.txt)
Guess.Queue......: 1/1 (100.00%)
Speed.#1.........:       29 H/s (34.32ms) @ Accel:4 Loops:4096 Thr:64 Vec:1
Speed.#2.........:       28 H/s (34.65ms) @ Accel:4 Loops:4096 Thr:64 Vec:1
Speed.#3.........:       29 H/s (34.35ms) @ Accel:4 Loops:4096 Thr:64 Vec:1
Speed.#4.........:       29 H/s (34.47ms) @ Accel:4 Loops:4096 Thr:64 Vec:1
Speed.#*.........:      114 H/s
Recovered........: 2/2 (100.00%) Digests (total), 2/2 (100.00%) Digests (new), 2/2 (100.00%) Salts
Progress.........: 70424/88784 (79.32%)
Rejected.........: 24/70424 (0.03%)
Restore.Point....: 33803/44392 (76.15%)
Restore.Sub.#1...: Salt:1 Amplifier:0-1 Iteration:864256-868352
Restore.Sub.#2...: Salt:1 Amplifier:0-1 Iteration:1044480-1048576
Restore.Sub.#3...: Salt:1 Amplifier:0-1 Iteration:892928-897024
Restore.Sub.#4...: Salt:1 Amplifier:0-1 Iteration:53248-57344
Candidate.Engine.: Device Generator
Candidates.#1....: patrick01 -> 101287
Candidates.#2....: 120486 -> bananasplit
Candidates.#3....: babygurl18 -> evander
Candidates.#4....: vanda -> astrid
Hardware.Mon.#1..: Temp: 70c Fan: 13% Util: 24% Core: 852MHz Mem: 167MHz Bus:16
Hardware.Mon.#2..: Temp: 74c Fan: 26% Util:  2% Core: 852MHz Mem: 167MHz Bus:16
Hardware.Mon.#3..: Temp: 68c Fan: 13% Util: 28% Core: 852MHz Mem: 167MHz Bus:16
Hardware.Mon.#4..: Temp: 69c Fan: 12% Util: 11% Core: 852MHz Mem: 167MHz Bus:16

Started: Mon May  6 13:29:13 2024
Stopped: Mon May  6 13:39:44 2024

@MrX0r
Copy link
Author

MrX0r commented May 6, 2024

Can you provide hash string and password? Are you using CUDA or OpenCL?

Hello @ventaquil
The problem only occurs when using CUDA, tests with Intel OpenCL work perfectly with a dictionary attack

On Linux there are no problems with CUDA and dictionary attack no problems with the latest repo

$bitlocker$0$16$5958450f3bd4d68a6abdd7bbd4462957$1048576$12$901e9a4c809fda0103000000$60$f7f672e27984d19ef0cbeac9506ee26e3249868c3769bb32a8afc63b132caf7ac0dddcd7d42ec6ced340964ff7b1059e9518590966232cd4baa2e148
Password: 12345678

@ventaquil
Copy link
Contributor

I am not able to verify on Windows, but on Linux works fine.

@MrX0r
Copy link
Author

MrX0r commented May 17, 2024

I am not able to verify on Windows, but on Linux works fine.

@ventaquil

Thank you very much, yes under linux there are no problems, which is very strange, someone needs to look at that. Why the error occurs on Windows.

@PenguinKeeper7
Copy link
Contributor

Works for me on Windows 10 Home with both CUDA and OpenCL. If no-one is able to recreate your issue, it may be an environment issue and not a Hashcat problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants