Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 0xaa-unsafe-consumption-of-apis.md #108

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion 2023/en/src/0xaa-unsafe-consumption-of-apis.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ API10:2023 Unsafe Consumption of APIs
| Threat agents/Attack vectors | Security Weakness | Impacts |
| - | - | - |
| API Specific : Exploitability **2** | Prevalence **2** : Detectability **1** | Technical **3** : Business Specific |
| Developers tend to trust but not verify in their endpoints which interact with external or third-party APIs. Successful exploitation of security flaws in these APIs can impact those relying on them. | Usually, API integrations rely on weaker security requirements such as those regarding transport security, authentication/authorization, and input validation and sanitization. | Exposure of sensitive information to unauthorized actors and many kinds of injections are common issues. |
| Developers often trust external or third-party APIs without proper verification, leaving their endpoints vulnerable to security flaws. | API integrations typically exhibit weaker security measures, such as transport security, authentication/authorization, and input validation and sanitization. | Common issues include unauthorized exposure of sensitive information and various types of injections. |

## Is the API Vulnerable?

Expand Down