ActivID administrator account takeover the story behind HID-... #1668
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 article describes an unauthenticated administrator account takeover in HID ActivID Appliance 8.5, tracked as HID‑PSA‑2025‑002. The bug is an authentication bypass in the internal SOAP JAX‑WS API exposed behind nginx and Oracle WebLogic. The post is very methodical: it first reconstructs the full web and Java architecture (nginx → WebLogic → EAR/WAR/EJB) and then drills into how JAX‑WS authentication is supposed to work, before showing how a flawed ThreadLocal session model allows attacke...
🔧 Technical Details
1. Abusing ThreadLocal-based authentication context in JAX‑WS handlers
The main trick is to exploit designs where per‑request authentication state is stored in a static
ThreadLocal<Subject>(or similar) and not cleared between requests. A JAX‑WSSOAPHandlerthat only updates this Subject when a custom auth header (e.g.,mySubjectHeader) is present, and silently does nothing if the header is missing, enables authentication bypass. Because application servers use thread pools, a worker thread may carry a previously authenticated admin Subject. By sending unauthenticated SOAP requests without the auth header, and ensuring they do not cause exceptions in the handler, an attacker can eventually land on that thread and have their request executed under the stale admin Subject. In any environment, if you see aThreadLocalsecurity context used this way, test by removing the auth header and repeatedly calling pri...🤖 Agent Actions
Summary:
Tests: Not run (not applicable).
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.