Exploiting Node.js deserialization bug for Remote Code Execution

[@МихаилТолкачев-й3м]

so this trick only works for nodejs...
eval almost like evil

[@anthonyalmaguer3562]

I keep getting invalid username type as a response. Any suggestions?

[@MarbewRecords]

the same dude... have you solved it?

[@nunonuk]

I also get that message, but the remote shell opens. So, objective accomplished...

[@behnamanisi1]

yeah u get that but then you will get a shell straight after :)

[@wr3nch0x1]

SyntaxError: Unexpected token
at Object.parse (native)
at Object.exports.unserialize (/home/sun/node_modules/node-serialize/lib/serialize.js:62:16)
at /home/sun/server.js:11:24
at Layer.handle [as handle_request] (/home/sun/node_modules/express/lib/router/layer.js:95:5)
at next (/home/sun/node_modules/express/lib/router/route.js:137:13)
at Route.dispatch (/home/sun/node_modules/express/lib/router/route.js:112:3)
at Layer.handle [as handle_request] (/home/sun/node_modules/express/lib/router/layer.js:95:5)
at /home/sun/node_modules/express/lib/router/index.js:281:22
at Function.process_params (/home/sun/node_modules/express/lib/router/index.js:335:12)
at next (/home/sun/node_modules/express/lib/router/index.js:275:10)

[@刘洋-i4d]

me too. How to solve it?

[@nicoyuri4586]

comment utiliser nod. js

[@tamirtian6334]

prefer

[@letianchou9204]

good

[@mkhello3434]

@@kademarlon2500 you are writing these comments under every offensive security video