CompTIA PT0-003 Exam - Topic 3 Question 16 Discussion

Actual exam question for CompTIA's PT0-003 exam

Question #: 16
Topic #: 3

A penetration tester wants to maintain access to a compromised system after a reboot. Which of the following techniques would be best for the tester to use?

AEstablishing a reverse shell

BExecuting a process injection attack

CCreating a scheduled task

DPerforming a credential-dumping attack

Show Suggested Answer

Suggested Answer: A

Capabilities: BeEF is equipped with modules to create CSRF attacks, capture session tokens, and gather sensitive information from the target user's browser session.

Drawbacks: While useful for reconnaissance, Maltego is not designed for exploiting web vulnerabilities like CSRF.

Metasploit (Option C):

Capabilities: While Metasploit can exploit some web vulnerabilities, it is not specifically tailored for CSRF attacks as effectively as BeEF.

Drawbacks: It does not provide capabilities for exploiting CSRF vulnerabilities.

Conclusion: The Browser Exploitation Framework (BeEF) is the most suitable tool for leveraging a CSRF vulnerability to gather sensitive details from an application's end users. It is specifically designed for browser-based exploitation, making it the best choice for this task.

Maltego (Option B):

theHarvester (Option D):

by Stephanie at Dec 09, 2024, 05:08 AM

Limited Time Offer

25%

Off

Get Premium PT0-003 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Annamaria

4 months ago

Process injection sounds risky, not sure it's the best choice here.

upvoted 0 times

...

Bulah

5 months ago

Wait, can you really maintain access just with a scheduled task?

upvoted 0 times

...

Tamra

5 months ago

Definitely agree with the scheduled task option!

upvoted 0 times

...

Omega

5 months ago

I think a reverse shell is more effective for quick access.

upvoted 0 times

...

Lilli

5 months ago

Creating a scheduled task is a solid way to maintain access.

upvoted 0 times

...

Rodrigo

6 months ago

I remember a similar question where creating a scheduled task was highlighted as a good way to ensure access after a reboot. It seems like the safest choice.

upvoted 0 times

...

Ressie

6 months ago

I recall that establishing a reverse shell is more about immediate access rather than persistence. I don't think it would survive a reboot.

upvoted 0 times

...

Almeta

6 months ago

I'm not entirely sure, but I feel like executing a process injection attack could also work. It seems like it could help maintain access, but I'm not confident.

upvoted 0 times

...

Julene

6 months ago

I think creating a scheduled task might be the best option here since it can survive reboots. I remember practicing that in a lab.

upvoted 0 times

...

Svetlana

6 months ago

I'm leaning towards the rSvetlanarse shell approach. It seems like the most straightforward way to maintain access.

upvoted 0 times

...

Daniela

6 months ago

Performing a credential-dumping attack could also work, but it might be riskier if the system is closely monitored.

upvoted 0 times

...

Felicitas

6 months ago

Creating a scheduled task sounds like a good idea. That way the system will automatically run your code after a reboot.

upvoted 0 times

...

Xuan

6 months ago

Hmm, I'm not sure about that. Wouldn't a scheduled task be a more reliable way to regain access?

upvoted 0 times

...

Staci

6 months ago

I think a reverse shell would be the best option here to maintain access after a reboot.

upvoted 0 times

...

Portia

11 months ago

Scheduled task? Sounds like a real snooze-fest. Where's the excitement in that?

upvoted 0 times

Pearly

10 months ago

Chun: That sounds more stealthy. Let's go with that option.

upvoted 0 times

...

Chun

10 months ago

User 2: That could work, but it might be risky. What about hiding a backdoor in a system service?

upvoted 0 times

...

Timothy

10 months ago

User 1: How about using a rootkit to maintain access?

upvoted 0 times

...

Gail

11 months ago

Process injection? That's like sneaking into a party through the kitchen door. Subtle, I like it.

upvoted 0 times

Karl

10 months ago

Using process injection can help the tester maintain persistence on the compromised system.

upvoted 0 times

...

Valda

10 months ago

It's definitely a sneaky way to stay in the system without being detected.

upvoted 0 times

...

Dell

10 months ago

Yes, process injection is a great technique for maintaining access after a reboot.

upvoted 0 times

...

Wava

11 months ago

Credential-dumping, huh? I'm not sure I want to go down that rabbit hole, but it could be juicy.

upvoted 0 times

Hobert

10 months ago

Credential dumping might be risky, but it could give us the access we need.

upvoted 0 times

...

Krissy

10 months ago

Maybe setting up a persistence mechanism could work.

upvoted 0 times

...

Chauncey

11 months ago

I think using a backdoor would be the best option.

upvoted 0 times

...

Timmy

11 months ago

Ooh, a reverse shell sounds fun! I can practically hear the system whispering 'hack me, hack me' already.

upvoted 0 times

...

Cory

12 months ago

Creating a scheduled task seems like the way to go. It'll give me persistent access even after a reboot.

upvoted 0 times

Maryann

11 months ago

Yes, creating a scheduled task will ensure persistent access to the compromised system.

upvoted 0 times

...

Tamar

11 months ago

Scheduled task is a good choice for maintaining access after a reboot.

upvoted 0 times

...

Ellsworth

1 year ago

I think creating a scheduled task could also work to maintain access after a reboot.

upvoted 0 times

...

Queenie

1 year ago

I agree with Sheldon, a reverse shell would allow for persistent access.

upvoted 0 times

...

Sheldon

1 year ago

I think establishing a reverse shell would be the best option.

upvoted 0 times

...