Skip to content

Commit 67d704e

Browse files
committed
updates
1 parent a1ae585 commit 67d704e

8 files changed

Lines changed: 44 additions & 1562 deletions

File tree

src/macos-hardening/macos-security-and-privilege-escalation/mac-os-architecture/macos-ipc-inter-process-communication/README.md

Lines changed: 0 additions & 858 deletions
This file was deleted.

src/network-services-pentesting/1521-1522-1529-pentesting-oracle-listener/README.md

Lines changed: 0 additions & 68 deletions
This file was deleted.

src/network-services-pentesting/pentesting-web/iis-internet-information-services.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -204,6 +204,31 @@ If you see an error like the following one:
204204
It means that the server **didn't receive the correct domain name** inside the Host header.\
205205
In order to access the web page you could take a look to the served **SSL Certificate** and maybe you can find the domain/subdomain name in there. If it isn't there you may need to **brute force VHosts** until you find the correct one.
206206

207+
## Decrypt encrypted configuration and ASP.NET Core Data Protection key rings
208+
209+
Two common patterns to protect secrets on IIS-hosted .NET apps are:
210+
- ASP.NET Protected Configuration (RsaProtectedConfigurationProvider) for web.config sections like <connectionStrings>.
211+
- ASP.NET Core Data Protection key ring (persisted locally) used to protect application secrets and cookies.
212+
213+
If you have filesystem or interactive access on the web server, co-located keys often allow decryption.
214+
215+
- ASP.NET (Full Framework) – decrypt protected config sections with aspnet_regiis:
216+
217+
```cmd
218+
# Decrypt a section by app path (site configured in IIS)
219+
%WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -pd "connectionStrings" -app "/MyApplication"
220+
221+
# Or specify the physical path (-pef/-pdf write/read to a config file under a dir)
222+
%WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -pdf "connectionStrings" "C:\inetpub\wwwroot\MyApplication"
223+
```
224+
225+
- ASP.NET Core – look for Data Protection key rings stored locally (XML/JSON files) under locations like:
226+
- %PROGRAMDATA%\Microsoft\ASP.NET\DataProtection-Keys
227+
- HKLM\SOFTWARE\Microsoft\ASP.NET\Core\DataProtection-Keys (registry)
228+
- App-managed folder (e.g., App_Data\keys or a Keys directory next to the app)
229+
230+
With the key ring available, an operator running in the app’s identity can instantiate an IDataProtector with the same purposes and unprotect stored secrets. Misconfigurations that store the key ring with the app files make offline decryption trivial once the host is compromised.
231+
207232
## Old IIS vulnerabilities worth looking for
208233

209234
### Microsoft IIS tilde character “\~” Vulnerability/Feature – Short File/Folder Name Disclosure

src/network-services-pentesting/pentesting-web/laravel.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -115,6 +115,23 @@ For example `http://127.0.0.1:8000/profiles`:
115115

116116
This is usually needed for exploiting other Laravel RCE CVEs.
117117

118+
### Fingerprinting & exposed dev endpoints
119+
120+
Quick checks to identify a Laravel stack and dangerous dev tooling exposed in production:
121+
122+
- `/_ignition/health-check` → Ignition present (debug tool used by CVE-2021-3129). If reachable unauthenticated, the app may be in debug or misconfigured.
123+
- `/_debugbar` → Laravel Debugbar assets; often indicates debug mode.
124+
- `/telescope` → Laravel Telescope (dev monitor). If public, expect broad information disclosure and possible actions.
125+
- `/horizon` → Queue dashboard; version disclosure and sometimes CSRF-protected actions.
126+
- `X-Powered-By`, cookies `XSRF-TOKEN` and `laravel_session`, and Blade error pages also help fingerprint.
127+
128+
```bash
129+
# Nuclei quick probe
130+
nuclei -nt -u https://target -tags laravel -rl 30
131+
# Manual spot checks
132+
for p in _ignition/health-check _debugbar telescope horizon; do curl -sk https://target/$p | head -n1; done
133+
```
134+
118135
### .env
119136

120137
Laravel saves the APP it uses to encrypt the cookies and other credentials inside a file called `.env` that can be accessed using some path traversal under: `/../.env`
@@ -205,6 +222,8 @@ Another deserialization: [https://github.com/ambionics/laravel-exploits](https:/
205222
* [laravel-crypto-killer](https://github.com/synacktiv/laravel-crypto-killer)
206223
* [PHPGGC – PHP Generic Gadget Chains](https://github.com/ambionics/phpggc)
207224
* [CVE-2018-15133 write-up (WithSecure)](https://labs.withsecure.com/archive/laravel-cookie-forgery-decryption-and-rce)
225+
* [CVE-2024-52301 advisory – Laravel argv env detection](https://github.com/advisories/GHSA-gv7v-rgg6-548h)
226+
208227

209228
{{#include ../../banners/hacktricks-training.md}}
210229

src/pentesting-web/web-vulnerabilities-methodology/README.md

Lines changed: 0 additions & 132 deletions
This file was deleted.

0 commit comments

Comments
 (0)