ISO-IEC-27001-LEAD-AUDITOR · Question #295
Scenario: A data processing tool crashed when a user added more data to the buffer than its storage capacity allows. The incident was caused by the tool's inability to bound-check arrays. What kind…
The correct answer is A. Intrinsic vulnerability, i.e., inability to bound-check arrays, is a characteristic of the data. Intrinsic vulnerabilities are inherent flaws in a system, software, or tool. In this case, the inability to bound-check arrays is an inherent weakness of the software, making it an intrinsic vulnerability. This aligns with ISO/IEC 27001:2022 Annex A Control A.8.9 (Configuration…
Question
Scenario:
A data processing tool crashed when a user added more data to the buffer than its storage capacity allows. The incident was caused by the tool's inability to bound-check arrays. What kind of vulnerability is this?
Options
- AIntrinsic vulnerability, i.e., inability to bound-check arrays, is a characteristic of the data
- BExtrinsic vulnerability, i.e., the exploit of the buffer overflow vulnerability, is caused by an external
- CNone; buffer overflow is not a vulnerability; it is a threat
How the community answered
(38 responses)- A87% (33)
- B8% (3)
- C5% (2)
Explanation
Intrinsic vulnerabilities are inherent flaws in a system, software, or tool. In this case, the inability to bound-check arrays is an inherent weakness of the software, making it an intrinsic vulnerability. This aligns with ISO/IEC 27001:2022 Annex A Control A.8.9 (Configuration Management), which mandates secure software design and validation practices. Extrinsic vulnerabilities arise due to external factors (e.g., misconfigurations or lack of security Buffer overflow is a vulnerability, not a threat, because it represents a weakness that can be exploited by an attacker.
Topics
Community Discussion
No community discussion yet for this question.