New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Solaris 'EXTREMEPARR' dtappgather Privilege Escalation module #10663
Add Solaris 'EXTREMEPARR' dtappgather Privilege Escalation module #10663
Conversation
Add 10u9 to the list.
|
11.3 fails (as expected since its not vulnerable, and the payload would have failed anyways)
|
10u2
|
end | ||
|
||
def exploit | ||
if is_root? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason this is here and not in check?
Knowing you, there was a thought process behind the decision, just curious for consistency in other modules.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if it were in check, it could be bypassed by the force exploit.
Not sure why someone would still want to run it while being root, but at least it leaves that option open
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@h00die It's nice to be able to run the check
method to determine whether a host is vulnerable, regardless of our current user context. The host is no more or less vulnerable if we're already root. If we're already root, the host isn't Safe
.
There's a separate issue here, which is that there are instances where we'll want to execute the module, even if we are already root
. In particular, the is_root?
check is not namespace safe. It's quite possibly we'll have a session in a user namespace as root
yet still want to execute the module to become real root UID 0.
I haven't had time to open an issue for discussion. My suggestion is to keep the is_root?
check outside of the check
method, while ensuring it is still included in a ForceExploit
conditional in each module. However #10622 needs to be resolved before a code pattern can be developed and implemented in every local exploit module.
Release NotesThe Solaris EXTREMEPARR dtappgather module has been added to the framework. It exploits a direct traversal vulnerability in the dtappgather executable that is included on unpatched Solaris systems 10u11 and older. You can achieve root access with this exploit. |
Add Solaris 'EXTREMEPARR' dtappgather Privilege Escalation module.
Verification
msfconsole
use exploit/solaris/local/extremeparr_dtappgather_priv_esc
set SESSION [SESSION]
run
Output