Timeline for How to pentest an AngularJS based SPA (Single Page Application)
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 13, 2023 at 9:51 | vote | accept | Jassi | ||
| Mar 5, 2021 at 14:31 | answer | added | deijmaster | timeline score: 5 | |
| Mar 2, 2021 at 15:37 | history | unprotected | atdre | ||
| Dec 14, 2017 at 10:00 | history | protected | CommunityBot | ||
| Aug 8, 2016 at 10:22 | comment | added | Serge Ballesta | Just generalities (so a comment and not an anwser...) but client side applications can be vulnerable to man in the middle: try to spy the exchanges with wireshark (if not encrypted) or with browser internal debugger to see whether it is possible to workaround any security through IHM with direct forged requests. | |
| Mar 11, 2016 at 23:38 | history | tweeted | twitter.com/StackSecurity/status/708436988479848449 | ||
| Mar 11, 2016 at 19:11 | answer | added | atdre | timeline score: 4 | |
| Mar 11, 2016 at 10:02 | review | First posts | |||
| Mar 11, 2016 at 12:12 | |||||
| Mar 11, 2016 at 9:59 | history | asked | Jassi | CC BY-SA 3.0 |