Skip to content

Commit dbe2524

Browse files
committed
docs: Add Threat Agend and Impacts
1 parent c21153c commit dbe2524

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

2019/en/0xa3-improper-data-filtering.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,14 +4,18 @@ A3:2019 Improper Data Filtering
44
| Threat agents/Attack vectors | Security Weakness | Impacts |
55
| -- | -- | -- |
66
| Access Lvl : Exploitability ? | Prevalence ? : Detectability ? | Technical ? : Business |
7-
| | | |
7+
| Since API are used as data sources, many times while writing the APIs developers try to implement them in a very generic way, without thinking about the sensitivity of the exposed data. They rely on clients to perform the data filtering before showing it to the user. | | Frequently sensitive object properties are exposed such as those holding PII protected by law or regulation (e.g. GDPR), authentication data or meaningful resources relationships. |
88

99
## Is the API Vulnerable?
1010

11-
## How To Prevent
12-
1311
## Example Attack Scenarios
1412

13+
### Scenario #1
14+
15+
### Scenario #2
16+
17+
## How To Prevent
18+
1519
## References
1620

1721
### OWASP

0 commit comments

Comments
 (0)