Skip to content

Commit

Permalink
fix busted image link
Browse files Browse the repository at this point in the history
  • Loading branch information
pburkholder committed Aug 15, 2018
1 parent 5eacc55 commit a56f42d
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,7 @@

This was inspired by, and originally forked from, code in https://github.com/mfdii/miner-blog, by [Michael Ducy](https://twitter.com/mfdii). That code accompanies [this blog post](https://sysdig.com/blog/detecting-cryptojacking-with-sysdigs-falco/), on Detecting Cryptojacking with Sysdig's [Falco](https://github.com/draios/falco).

I munged it for use in an incident response exercise with Cloud Foundry. It uses an Immediately-Invoked Function Expression attack on a NodeJS application to run arbitrary code in a container. The vulnerable application is in `node-exploitable/`, and relies on [node-serialize 0.0.4](https://github.com/luin/serialize) which has a [known, unpatched, 2017 CVE](https://www.cvedetails.com/vulnerability-list/vendor_id-16128/product_id-36008/version_id-208749/Node-serialize-Project-Node-serialize-0.0.4.html). As a result, I see this
![warning in GitHub](./node-serialize-warning.png):
I munged it for use in an incident response exercise with Cloud Foundry. It uses an Immediately-Invoked Function Expression attack on a NodeJS application to run arbitrary code in a container. The vulnerable application is in `node-exploitable/`, and relies on [node-serialize 0.0.4](https://github.com/luin/serialize) which has a [known, unpatched, 2017 CVE](https://www.cvedetails.com/vulnerability-list/vendor_id-16128/product_id-36008/version_id-208749/Node-serialize-Project-Node-serialize-0.0.4.html). As a result, I see this warning in GitHub:

> ⚠️ We found a potential security vulnerability in one of your dependencies. A dependency defined in node-exploitable/package-lock.json has known security vulnerabilities and should be updated.
Expand Down

0 comments on commit a56f42d

Please sign in to comment.