Think Positive Cyber

CompTIA Security+ SY0-701 covers both human-based attacks and technical application vulnerabilities. Three important concepts are pretexting, memory injection, and TOC/TOU vulnerabilities.

Although they describe very different attacks, each involves an attacker taking advantage of trust, timing, or the normal operation of a system.

What Is Pretexting?

Pretexting is a social engineering technique in which an attacker invents a believable situation or story to convince someone to reveal information or perform an action.

The attacker creates a pretext, meaning a false reason for the interaction.

For example, someone might pretend to have a legitimate business reason for requesting sensitive information.

The important Security+ relationship is:

False scenario or situation → Pretexting

Impersonation and pretexting can occur together, but they describe different elements of an attack.

Impersonation focuses on pretending to be another person or entity.

Pretexting focuses on creating the believable story or situation used to manipulate the victim.

Think:

Impersonation → Who am I pretending to be?

Pretexting → What story am I telling?

What Is Memory Injection?

Memory injection is an application attack involving the introduction of external code into the address space of a running program.

The critical words are:

External code + running program → Memory injection

This distinguishes memory injection from a buffer overflow.

A buffer overflow occurs when a program writes beyond the intended boundaries of a memory buffer.

Memory injection instead focuses on placing or introducing code into the memory space of a process that is already running.

What Is TOC/TOU?

TOC/TOU stands for Time of Check / Time of Use.

This vulnerability exists when a system checks the state of a resource and then uses the resource later. The resource may change during the time between those two operations.

The important relationship is:

Check something → It changes → Use it

That sequence describes a TOC/TOU vulnerability.

TOC/TOU vulnerabilities are associated with race conditions because the timing of operations can allow an attacker or another process to change something after it has been checked but before it is used.

A simple conceptual example is:

1. A program checks whether access to a resource is allowed.
2. Something about the resource changes.
3. The program uses the resource based on the earlier check.

The security decision may now be based on information that is no longer valid.

The three key associations are therefore:

False scenario → Pretexting

External code inside a running program → Memory injection

Check first, change occurs, use later → TOC/TOU

These concepts are valuable for recognizing social engineering attacks, application attacks, race conditions, memory vulnerabilities, and software security weaknesses while preparing for the CompTIA Security+ SY0-701 certification exam in 2026.