mirror of
https://github.com/HackTricks-wiki/hacktricks-cloud.git
synced 2026-06-12 11:01:38 -07:00
Update README.md
This commit is contained in:
@@ -841,8 +841,6 @@ Invoke-AzureRmVMBulkCMD -Script Mimikatz.ps1 -Verbose -output Output.txt
|
||||
|
||||
Azure VMs expose **internal platform endpoints** that are used for configuration, metadata retrieval and identity management. Understanding the difference between them is critical for **enumeration, privilege escalation and post-exploitation**.
|
||||
|
||||
---
|
||||
|
||||
### Wire Server (Azure Fabric Endpoint)
|
||||
|
||||
The **Azure WireServer** is an internal Azure IP (`168.63.129.16`) used by the platform to communicate with the VM.
|
||||
@@ -857,8 +855,6 @@ It is responsible for:
|
||||
- DHCP & DNS services
|
||||
- Health monitoring
|
||||
|
||||
---
|
||||
|
||||
### GoalState & ExtensionsConfig
|
||||
|
||||
The **GoalState** represents the **desired configuration of the VM** as defined by Azure. It may include:
|
||||
@@ -901,14 +897,10 @@ This is because:
|
||||
- Requests may require **specific headers, timing, or context**
|
||||
- Some responses are only available to the **VM Agent execution environment**
|
||||
|
||||
---
|
||||
|
||||
### Run Command vs SSH Context
|
||||
|
||||
Azure provides multiple ways to execute commands inside a VM, but **they do not run in the same context**.
|
||||
|
||||
---
|
||||
|
||||
#### Run Command
|
||||
|
||||
Run Command is an Azure feature that executes scripts via the **VM Agent**.
|
||||
|
||||
Reference in New Issue
Block a user