Details
Minor Description
A Nessus scan pinged my test cluster because the Accumulo monitor allows HTTP TRACE requests. (ref: an overview of the general problem class)
The issue isn't bad unless
- there's a same-origin-policy bypass for the user browser
- there's an auth token we care about
Exploits the bypass the same-origin-policy happen, so it's best to clean up server side if possible.
The only auth tokens present in the Monitor are when we make use of the ShellServlet from ACCUMULO-196. We rely on the session state for auth, so there isn't a risk of leaking auth info directly, but we would leak the session id.
The CSRF added in ACCUMULO-2785 means just the session id wouldn't be enough for impersonation, but if an attacker can read one requested page we have to presume they can read another.
We should clean up our configs to disallow HTTP TRACE as a proactive measure.
Marking minor since an attack vector would need an enabling vulnerability on the client side.
