Prepping for tomorrow's interview. (I don't really have a lot of actual work to do.) It seems like one of their production sites is vulnerable to a CSRF attack, they aren't using a Content Security Policy (though they do take some steps for XSS attack prevention), and their CORS policy seems awfully permissive. I'm gathering some questions.
'War Stories'
Natter 76: Life, Liberty, and the Pursuit of Foaminess
Off-topic discussion. Wanna talk about corsets, duct tape, butt kicking, or physics? This is the place. Detailed discussion of any current-season TV must be whitefonted.
I really really dislike getting emails from teachers about work not being done. Last week was a nonstop push to get things done and turned in and the whole time there was s long term project he should have also been working on that he was not.
I think they are using AWS elastic load balancer cookies for their session id and they are readable by javascript. That doesn't seem good. And the cookies aren't marked as secure which also doesn't seem good.
Seven to ten propane takes in a minivan in the parking garage adjacent to our loading dock. Three of the 4 corners surrounding the block were blocked off.
Hmmm.... I can trace their redux actions on a production site. That doesn't seem ideal either. They do address clickjacking though.
No e-mail validation. That's just weird.
Check you spam folder.
They just don't validate. OTOH, my simple XSS and SQL injection attacks are getting nowhere. That's good.
"Hi, you should hire me because I casually hacked into your system yesterday. Your security sucks. Here's the upcoming stock report from the CEO's draft folder."
Oh I'm just doing some gentle probing to see if I can find security flaws. They don't seem vulnerable to causal attacks, but I think there is some vulnerability to a determined attack.