Insecure Direct Object References (IDOR) occur when an application provides direct access to objects based on user-supplied input. In the provided URLs, the userid parameter is directly referenced, which can allow attackers to manipulate these references to access unauthorized data. This vulnerability can lead to unauthorized access to other users' profiles by simply changing the userid parameter value. The other vulnerabilities listed (Improper error handling, Race condition, Weak or default configurations) do not directly relate to the issue demonstrated by the URLs.

Reference: https://kirkpatrickprice.com/blog/stages-of-penetration-testing-according-to-ptes/

A SYN flood attack exploits the TCP handshake by sending a succession of SYN requests to a target's system. Each request initializes a connection that the target system must acknowledge, thus consuming resources.
Step-by-Step Explanation
Understanding the Script:
ip = IP("192.168.50.2"): Sets the destination IP address to 192.168.50.2.
tcp = TCP(sport=RandShort(), dport=80, flags="S"): Creates a TCP packet with a random source port, destination port 80, and the SYN flag set.
raw = RAW(b"X"*1024): Adds 1024 bytes of data to the packet.
p = ip/tcp/raw: Combines the IP, TCP, and RAW layers into a single packet.
send(p, loop=1, verbose=0): Sends the packet in an infinite loop without verbose output.
Purpose of SYN Flood:
Resource Exhaustion: By sending numerous SYN requests, the target's connection table fills up, preventing legitimate connections.
Denial of Service: The target system becomes overwhelmed and unable to process further requests, effectively causing a denial of service.
Detection and Mitigation:
Rate Limiting: Implement rate limiting on SYN packets.
SYN Cookies: Use SYN cookies to handle the connection requests without allocating resources immediately.
Firewalls and IDS: Deploy firewalls and Intrusion Detection Systems (IDS) to detect and mitigate SYN flood attacks.
Reference from Pentesting Literature:
SYN flood attacks are a classic example of a denial-of-service attack and are commonly discussed in penetration testing guides and HTB write-ups for understanding network-based attacks.
Reference:
Penetration Testing - A Hands-on Introduction to Hacking
HTB Official Writeups

Netcat is a versatile networking utility which reads and writes data across network connections, using the TCP/IP protocol. It's included in many Linux distributions and is available for Windows as well. Since the requirement is to use only local operating system tools for file transfer, Netcat is a suitable option because it can easily be scripted or used directly from the command line to send and receive files, making it a powerful tool for file transfers in a penetration testing context. Options B and C, WinSCP and Filezilla, are not typically considered local operating system tools as they are third-party applications that need to be installed.
Option D, Netstat, is a network utility that displays network connections, routing tables, and a number of network interface and network protocol statistics, and is not used for file transfers.

The DREAD model is a risk assessment framework used to evaluate and prioritize the security risks of an application. It stands for Damage potential, Reproducibility, Exploitability, Affected users, and Discoverability.
Step-by-Step Explanation
Understanding DREAD:
Purpose: Provides a structured way to assess and prioritize risks based on their potential impact and likelihood.
Components:
Damage Potential: The extent of harm that an exploit could cause.
Reproducibility: How easily the exploit can be reproduced.
Exploitability: The ease with which the vulnerability can be exploited.
Affected Users: The number of users affected by the exploit.
Discoverability: The likelihood that the vulnerability will be discovered.
Usage in Threat Modeling:
Evaluation: Assign scores to each DREAD component to assess the overall risk.
Prioritization: Higher scores indicate higher risks, helping prioritize remediation efforts.
Process:
Identify Threats: Enumerate potential threats to the application.
Assess Risks: Use the DREAD model to evaluate each threat.
Prioritize: Focus on addressing the highest-scoring threats first.
Reference from Pentesting Literature:
The DREAD model is widely discussed in threat modeling and risk assessment sections of penetration testing guides.
HTB write-ups often include references to DREAD when explaining how to assess and prioritize vulnerabilities in applications.
Reference:
Penetration Testing - A Hands-on Introduction to Hacking
HTB Official Writeups