The correct answer is:
C. Memory injection
Explanation:
Memory injection involves injecting malicious code or data into the memory of a running process or the operating system itself. This type of exploit allows the attacker to bypass traditional detection methods, as the malicious code is executed directly in memory and does not necessarily touch the file system. Since it is executed in memory, it can evade detection by antivirus software or other file-based security measures, allowing the exploit to go undetected by the operating system.
A. Firmware vulnerabilities: Firmware operates at a lower level than the operating system. It's the software embedded in hardware components like the BIOS/UEFI, network cards, hard drives, etc. If a vulnerability exists in the firmware, an exploit can run before the operating system even boots or can operate outside of the OS's control.
NOT C. Memory injection: Memory injection involves inserting malicious code directly into a running process's memory. While this can be a powerful technique, the operating system's memory management and security features can potentially detect anomalies, especially if the injected code attempts unauthorized actions.
Firmware vulnerabilities are often overlooked and can provide attackers with persistent access to a system, even after a full operating system reinstall. Firmware is the low-level software that controls hardware devices, and vulnerabilities in firmware can allow attackers to gain unauthorized access to a system and its data.
Firmware operates at a lower level than the operating system (OS), controlling hardware components directly. Exploiting firmware vulnerabilities allows attackers to bypass the operating system's security mechanisms, enabling the exploit to go undetected by the OS. Since firmware runs before the OS boots, malicious code in firmware can persist and remain hidden from the OS and its monitoring tools.
Memory injection is the most direct technique that allows an exploit to go undetected by the operating system because it allows malicious code to run in the system's memory without leaving traces on disk, evading file-based detection systems
Memory injection involves injecting malicious code directly into the memory space of a running process, bypassing the operating system's file-based security checks.
Memory injection is a technique where malicious code is injected directly into the memory space of a running process, allowing the exploit to execute without being written to disk. This makes it difficult for the operating system and traditional antivirus software to detect, as there are no files or persistent artifacts for security tools to analyze.
Firmware vulnerabilities are often overlooked and can provide attackers with persistent access to a device, even after a full operating system reinstallation. This is because firmware is deeply embedded in the hardware and can be difficult to update or patch.
I would disagree and stick to C. Memory injection, as while firmware vulnerabilities can be dangerous, they do not specifically allow exploits to go undetected by the operating system. They may affect the firmware level, which is below the OS and hence stay persistent despite OS reinstall, but detection by the OS is not always bypassed.
Meanwhile memory injection is ephemeral and often is injected into running processes, hence avoiding potential detection by AV
upvoted 4 times
...
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
jbmac
1 week, 5 days agolaternak26
2 weeks, 2 days agoProudFather
3 weeks, 4 days agoExam_Prep221
3 weeks, 5 days agoFourgehan
1 month, 1 week agochasingsummer
1 month, 3 weeks ago9ef4a35
1 month, 3 weeks agoEmmyrajj
1 month, 3 weeks agojacobtriestech
1 month, 3 weeks agodrivinglama
1 month, 3 weeks ago