HTB WhiteRabbit n8n HMAC Forgery, SQL Injection, restic Abus... #1670
+171
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
This post walks through a full compromise chain of the HackTheBox machine WhiteRabbit, starting from web recon, abusing a WebSocket-based Uptime Kuma login, discovering internal services, exploiting an n8n signed webhook SQL injection, abusing restic for container root, pivoting to the host via leaked SSH keys, and finally exploiting a time-seeded password generator to become root on the host.
1. Recon and Topology
The attacker scans the targe...
🔧 Technical Details
WebSocket Auth Bypass via Tampering Server Responses
When a web app uses Socket.IO/WebSockets for login and the front-end trusts a simple server flag like
{"ok": false}, an attacker can intercept server-to-client frames (e.g., in Burp) and flipfalsetotrue. With interception left enabled to stall further WebSocket traffic, the UI may render as logged-in long enough to inspect configuration/version data (e.g., Uptime Kuma Settings → About) even though the user is never truly authenticated.Finding Internal Assets via Public Uptime Kuma Status Pages
Uptime Kuma exposes public status dashboards at
/status/<slug>. Brute-forcing slugs (e.g., with Feroxbuster) against/statusoften reveals operational dashboards that enumerate internal services, each with explicit hostnames (e.g., GoPhish and WikiJS on internal subdomains). These domains usually sit behind auth but are network-reachabl...🤖 Agent Actions
Summary:
src/pentesting-web/websocket-attacks.mdwith a new section on tampering server-to-client Socket.IO frames to trigger client-side logins for reconnaissance, and referenced the HTB WhiteRabbit case.src/network-services-pentesting/pentesting-web/web-api-pentesting.mdby detailing how leaked low-code workflow exports can be used to recompute webhook HMACs and by providing a mitmproxy addon plus workflow for transparently re-signing requests during automated exploitation.src/pentesting-web/sql-injection/README.mdwith guidance on exploiting n8n-style templated SQL nodes, including error reflection, signing requirements, and automation tips, and added the related reference.src/linux-hardening/privilege-escalation/README.md, covering credential leakage from logs, restic loot recovery, and usingsudo resticas a root execution primitive, and cited the new source.src/crypto-and-stego/crypto-ctfs-tricks.mdwith a section on predicting time-seeded libcrand()password generators (including a helper script) and introduced a references section citing the blog.Tests: Not run (not requested).
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.