Update 0xaa-unsafe-consumption-of-apis.md #136
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The problem is not the endpoint itself, but what happens under the hood, that is the lack of verification on the interactions with the external parties: a developer can implement an API that correctly validates the input from the user, however this doesn't solve the lack of verification with the third party.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here I think that the object complement "endpoints" in the sentence "Developers tend to trust and not verify the endpoints [,,,]" is wrong, the problem is not trusting and not-verifying the developer's endpoint, but trusting and not-verifying the interactions with the external parties.