Chapter 3 - Threats in Software Continued

Question 1

Input attacks

Answer 1

• Definition: Input attacks exploit application weaknesses, causing unexpected behavior such as elevation of privileges, execution of arbitrary code, malfunction, or application abort.
• Types of Input Attacks: Buffer overflow, integer overflow, SQL injection, script injection, cross-site scripting (XSS), cross-site request forgery (CSRF).
• Countermeasures: Effective input field filtering, application firewall, application vulnerability scanning, developer training.

Question 2

Object Reuse

Answer 2

• Definition: Object reuse vulnerabilities occur when processes or applications unintentionally share or expose residual data that can be exploited.
• Countermeasures: Application isolation, server virtualization, developer training.

Question 3

Mobile Code

Answer 3

• Definition: Mobile code includes executable content that can be downloaded or transferred for execution on another system, potentially posing security risks.
• Countermeasures: Anti-malware protection, reduced user privileges, mobile code access controls, application whitelisting, secure workstation configuration.

Question 4

Social Engineering

Answer 4

• Definition: Social engineering attacks manipulate individuals to gain sensitive information or unauthorized access by exploiting human trust and helpfulness.
• Countermeasures: Education and training, clear procedures for information requests, restricted access to sensitive information.

Question 5

Back Door

Answer 5

• Definition: Back doors are hidden mechanisms deliberately planted in applications to bypass security for various purposes, including testing, production access, or unauthorized access.
• Countermeasures: Code reviews, source code control, source code scanning, data loss prevention (DLP), third-party code reviews and assessments.

Question 6

Logic Bomb

Answer 6

• Definition: Logic bombs are instructions placed in code to perform harmful actions when a predetermined condition is met, often activated by a specific date or event.
• Countermeasures: Code reviews, source code control, source code scanning, third-party code reviews and assessments.