XML processing modules may be not secure against maliciously constructed data. An attacker could abuse XML features to carry out denial of service attacks, access logical files, generate network connections to other machines, or circumvent firewalls.
The penetration tester running XML tests against application will have to determine which XML parser is in use, and then to what kinds of below listed attacks that parser will be vulnerable.
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
| # docker-ls and docker-rm from https://github.com/mayflower/docker-ls | |
| $ docker-ls repositories --registry https://docker-registry-test.es.dus1.cloud --level 1 | |
| requesting list . done | |
| repositories: [] | |
| $ docker push docker-registry-test.es.dus1.cloud/es/docker-registry:master | |
| The push refers to repository [docker-registry-test.es.dus1.cloud/es/docker-registry] | |
| b91fa4df7d25: Pushed | |
| a19cbdf71876: Pushed |
Jon Warbrick, July 2014, V3.2 (for Ansible 1.7)
First one found from of
| ### Keybase proof | |
| I hereby claim: | |
| * I am inka on github. | |
| * I am inka (https://keybase.io/inka) on keybase. | |
| * I have a public key whose fingerprint is 45B1 5A7B 2E4A B5AC E28C 6803 58B3 1C8F 594C A7F8 | |
| To claim this, I am signing this object: |
