feat: fixing stegonography #636
Open
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
willgvfranco
force-pushed
the
feat/stegonography
branch
from
c421269 to
140755a
Compare
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.
This solution refers to which of the apps?
A/M# - App's name here
What did you do to mitigate the vulnerability?
A clear and concise description of what you did. Keep in mind that, if your solution is accepted, this PR will be listed as possible solutions, so do your best to explain it clearly! 😁
Images are not necessary but are greatly appreciated! 📸
Did you test your changes? What commands did you run?
A good place to start would be trying to reproduce the attack narrative and not being able to successfully exploit the app anymore.