Magento CosmicSting XXE Testbed #9
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
There was a problem hiding this comment.
Hi @lokiuox,
thank you for your contribution. The testbed is easy to deploy and is working correctly. Ideally you should add a way to test manually if the testbed is vulnerable or not. I don't know how feasible could be in this case.
Feel free to reach out
|
LGTM. |
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.
Pretty straightforward testbed with the 2 testbeds for the vulnerable and safe configurations.
About the safe one, turns out the latest Magento image hosted on bitnami is still vulnerable, so I had to manually apply the patch released by Adobe. When bitnami updates the image to a patched one we can consider just changing the version number in the compose file and remove the manual patching.