From 586f473ffe3bec2e7f85c0ce32ff55f9380de3e3 Mon Sep 17 00:00:00 2001 From: Francois Marier Date: Sun, 8 Feb 2026 14:26:59 -0800 Subject: [PATCH] Fix typo in A10_2025-Mishandling_of_Exceptional_Conditions --- 2025/docs/en/A10_2025-Mishandling_of_Exceptional_Conditions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2025/docs/en/A10_2025-Mishandling_of_Exceptional_Conditions.md b/2025/docs/en/A10_2025-Mishandling_of_Exceptional_Conditions.md index 6fdb956e4..a76495321 100644 --- a/2025/docs/en/A10_2025-Mishandling_of_Exceptional_Conditions.md +++ b/2025/docs/en/A10_2025-Mishandling_of_Exceptional_Conditions.md @@ -68,7 +68,7 @@ Exceptional conditions can be caused by missing, poor, or incomplete input valid Many different security vulnerabilities can happen when we mishandle exceptional conditions, -such as logic bugs, overflows, race conditions, fraudulent transactions, or issues with memory, state, resource, timing, authentication, and authorization. These types of vulnerabilities can negatively affect the confidentiality, availability, and/or integrity of a system or it’s data. Attackers manipulate an application's flawed error handling to strike this vulnerability. +such as logic bugs, overflows, race conditions, fraudulent transactions, or issues with memory, state, resource, timing, authentication, and authorization. These types of vulnerabilities can negatively affect the confidentiality, availability, and/or integrity of a system or its data. Attackers manipulate an application's flawed error handling to strike this vulnerability. ## How to prevent.