hello and welcome to another application of the minor attack framework discussion Today. We're looking at elevated execution with Prompt. So let's go ahead and jump into our objectives.
So today's objectives are as follows. We're going to describe elevated execution with prompt. So the name has a lot to say about what we're going to be doing here.
How has elevated execution with prompt been used? We're going to look at some mitigation techniques, and then we're going to talk detection techniques as well.
elevated execution with prompts a threat. Actors use authorization. Execute with privilege AP Eyes to escalate privileges by prompting the user for credentials. So that is a mouthful.
The A P I has no validation to determine if the request has come from a reputable source. And so a key thing here
anybody can pretty much put something in here, and it will attempt to get the user to provide credentials. Teoh provide you no additional privileges, and so this could be abused. In that threat, actors will install malicious software and other persistence mechanisms by taking advantage of this a p I
so very interesting, right? So we have something built in probably developed for, you know, good causes
that someone has found in their able to manipulate through this this particular loophole. So that's very interesting. So let's talk about an instance where this is used.
And so there's actually a Mac OS malware variant called Slayer. And essentially, this malware attempts to get the user to install malicious updates claiming to be for Flash Player.
And so, essentially, the Mauer does some of the following things. It will collect system information such as Mats, Mac Version and I O platform. Do you I d.
It will generate assist a session. Do you? I d using the you you I degen command. It creates a custom. You are l using the information from these given steps. And then it will attempt to download a zip file payload using curl creates a directory and unzips
makes the binary executes the payload performs a kill on. So all this happens in pretty
rapid succession. But essentially, this is mimicking or looking much like the elevated execution with prompt a sfar us how this ax you go out,
you do something that you think is is legit like downloading an update or something of that nature, you're convinced that it's necessary your prompted to enter credentials to maybe give a pseudo or some type of domain administrator, local administrator privilege. You do so and then they've got you. So
you really have to make sure that you're paying attention. And a big part of this is going to be, you know, user education and understanding how these things work.
But there are also some techniques we can use for mitigation as well. So with respect to mitigation activities in the case of the Mac, we can prevent applications from running that haven't been downloaded through the Apple store. And so
not to say that trust is 100% here. But it's a little bit harder from a quality control standpoint to just throw something on there.
Um, and it be infected. But it happens, and so that's not foolproof. But it's definitely, you know, reducing some risk and do not allow unsigned applications to be run on the system at all again.
Not foolproof. But there's a little extra work that a threat actor would have to put in in order to circumvent some of these controls and do these things and then, from a detection standpoint,
we can consider monitoring for the user live e x e c slash security underscore. And then this is off
trampoline executions, which could indicate that, um,
the authorization execute with privileges is being executed. So a lot of jumbled words there, but that is exactly what you could do to help t provide some type of detection in this particular case.
Now, true or false, Max are not susceptible to malware or viruses.
All right, well, we're not going to take too long on this when this is definitely false because we just went over a particular malware variant that is Mac oriented. Now I know that it seems like we jump through some hoops pretty quickly here, but essentially
some other things to consider. When we talk about this particular type of elevated execution with prompt
is remember that if our users don't have privileges to install APS and do things of that nature, it could also work is a mitigating factor in our favor and then user education, While not mentioned in every instance with respect to detection and maybe even mitigation
is important with respect to them being able to know when something may be bogus, or to know when they are potentially being manipulated by a threat actor. So those are always going to be things that we want to bring up from time to time. Ah, and implement where we can.
So, in summary of today's discussion, we described elevated execution with prompt.
We described how elevated execution with prompt has been used in the Mac OS version of this discussion as well, describes a mitigation techniques and describe some detection techniques as well. So with that in mind, I want to thank you for your time today, and I look forward to seeing you again soon.