Information Security

Triple DES (3DES) is a symmetric encryption algorithm that provides confidentiality for personal data. XOR with a random number is not a standardized encryption method, DES-CBC with 56-bit keys is cryptographically broken, and salted hashing is one-way (cannot decrypt to retrieve the original data).

XSS attacks execute malicious scripts in the victim's browser, compromising the client. The vulnerability exists in the web application, but the attack impact is on the client side where the malicious code runs.

To solve this question, the user needs to know the purpose of cookie flags and how they are used to control cookie behavior.

A. Secure: This option is correct. When the "Secure" flag is set for a cookie, it instructs the browser to only send the cookie over a secure (HTTPS) connection. This prevents the cookie from being transmitted over an insecure (HTTP) channel where it could potentially be intercepted by an attacker.

B. Domain: This option is incorrect. The "Domain" flag is used to specify the domain(s) to which the cookie should be sent. It does not affect whether or not the cookie is transmitted over a secure channel.

C. Expires: This option is incorrect. The "Expires" flag is used to set an expiration date/time for the cookie. It does not affect whether or not the cookie is transmitted over a secure channel.

D. Static: This option is incorrect. There is no "Static" flag for cookies.

Therefore, the answer is: A. Secure

XSS attacks primarily compromise users by stealing session tokens, credentials, or performing actions on their behalf. While data integrity can be affected, the main risk is user account takeover through session hijacking.

All HTTP headers (Host, Cookie, Referrer) are user-controlled and can be manipulated by attackers. Every header must be validated before use to prevent injection attacks, cache poisoning, or authentication bypass.

Administrator accounts hold elevated privileges, making them high-value targets. Consequently, authentication requirements for administrators must be greater (e.g., multi-factor authentication, stricter password policies) than those for normal users. Distractors recommending equivalent, lesser, or no authentication increase system risk.

Hardcoding credentials cannot be treated as a secure practice because they are stored in plain text or easily decompilable code, exposing them to anyone with source access. Distractors suggesting it hides passwords, or is acceptable for internal or external facing applications, violate fundamental credential management principles.

To solve this question, the user needs to know about format string attacks and their consequences.

A format string attack occurs when a web application uses unvalidated input in a format string function. This can allow an attacker to read or write memory at will, which can lead to serious security issues.

Option A is incorrect. While the %s token can be used to read data from memory, it is not limited to "certain memory areas." Rather, it allows an attacker to read any data that is on the stack or heap.

Option B is incorrect. While other tokens can be used to write to memory, they are not limited to "certain areas." Rather, they allow an attacker to write to any address that is on the stack or heap.

Option C is correct. With a successful format string attack, an attacker can read and write to memory at will. This can allow the attacker to access sensitive data, modify program behavior, or even execute arbitrary code.

Option D is incorrect. A successful format string attack can have serious consequences, making this option incorrect.

Therefore, the answer is: C.

To understand what "White List" data validation means, the user needs to know the basics of data validation and filtering.

"White List" data validation refers to the process of validating data against a list of values that are known to be valid. This means that the data is filtered and compared against a pre-defined list of acceptable values. If the data matches any of the values on the list, it is considered valid. If it does not match any of the values on the list, it is considered invalid.

Option A is the correct answer, as it accurately describes what "White List" data validation means.

Option B is incorrect, as it describes the opposite of what "White List" data validation means.

Option C is incorrect because it includes option B, which is incorrect.

Option D is also incorrect because "White List" data validation is a real concept and option A accurately describes it.

The Answer is: A

To solve this question, the user needs to be familiar with the concept of different types of security vulnerabilities.

The answer to this question is A. Cross-Site Scripting (XSS).

Explanation:

A Cross-Site Scripting (XSS) attack occurs when an attacker injects malicious code into a web page that is viewed by other users. This attack typically takes advantage of vulnerabilities in web applications that do not properly validate user input.

In an XSS attack, the attacker may insert malicious code into a link that appears to be from a trustworthy source, such as a social networking site or an online banking application. When the victim clicks on the link, the malicious code is executed, allowing the attacker to steal sensitive information or take control of the victim's computer.

Option B, Buffer overflows, is a type of vulnerability that occurs when a program attempts to write more data to a buffer than it can hold. This can allow an attacker to overwrite critical data or execute malicious code.

Option C, Command injection, is a type of vulnerability that occurs when an attacker is able to execute arbitrary commands on a target system. This can allow the attacker to gain unauthorized access or perform other malicious actions.

Option D, Path traversal attack, is a type of vulnerability that occurs when an attacker is able to navigate to directories or files outside of the web root directory. This can allow the attacker to access sensitive files or execute malicious code.

Therefore, the correct answer is A. Cross-Site Scripting (XSS).

Blacklist validation is weak because it tries to block known bad inputs, which attackers can easily bypass using alternative encodings, alternate representations, or obfuscation that the filters do not cover. Distractors incorrectly blame hardcoding, HTTP POST complexity, or confuse blacklists with whitelist-oriented regular expressions.

Rejecting invalid input outright and sending an error is the most secure response because it avoids processing potentially malicious payloads. Escaping or deleting characters can result in bypasses (e.g., nested sanitization bypasses) or unintended data modification, while accepting it and merely logging is completely insecure.

Directory traversal (also called path traversal) attacks manipulate file paths using sequences like '../' to access files and directories outside the web document root. This can reveal source code, configuration files, or execute arbitrary files.

To prevent dictionary attacks on password hashes, one common technique is salting the hash.

Option A: Hashing the password twice is not a solution to prevent dictionary attacks. It is a technique called key stretching that makes brute-force attacks slower, but it does not prevent dictionary attacks.

Option B: Encrypting the password using the private key is not a solution to prevent dictionary attacks. Encryption is reversible, and an attacker with the private key can easily obtain the original password.

Option C: Using an encryption algorithm you wrote yourself is not a solution to prevent dictionary attacks. It is not recommended to invent your own encryption algorithm because it can have vulnerabilities that attackers can exploit.

Option D: Salting the hash is a technique that involves adding a random string of characters to the password before hashing. The salt is unique for each password and makes it difficult for an attacker to use precomputed hash tables (rainbow tables) to find the original password. Therefore, it is an effective method to prevent dictionary attacks.

Therefore, the correct answer is:

The Answer is: D

Hardcoded IP addresses are inflexible, difficult to maintain, and provide a false sense of security since IPs can be spoofed or change. Proper authentication and authorization should be based on user identity, not network location.