About JSFoo Coimbatore
JSFoo Coimbatore is a single-day conference with talks, Birds of Feather (BOF) sessions and speaker connect sessions. The conference will be held on Friday, 5 July, The Residency Tower, Coimbatore.
JSFoo Coimbatore features talks on:
- How to secure your web applications by identifying vulnerabilities.
- Leveraging OSINT to identify overly permissive application programming interfaces, business logic errors, insecure direct object reference attacks and use of insecure identifiers.
- Case studies of performance improvements and using the modular approach to building front-ends.
- Node.js and good engineering practices such as logging, debugging and integrating security into your applications.
For inquiries on tickets and sponsorships, call the JSFoo Coimbatore team on 7676332020 or write to us on firstname.lastname@example.org
Architect for scale: case studies of my learnings with Node.js
- Why this talk
- How not to do Logging
- My experience with security and JWT
- JSON vs. RPC
- Why “express” isn’t the answer to every problem
- Detecting and debugging memory leaks in production.
- Network and service mesh layer
- When to use HAProxy (vs. nginx)
- Bits of bad code I have seen
- Conclusion and QA
WebSDK: switching between service providers on the fly.
This talk is about sharing an experience that I had while solving a challenging problem. While discussing about the service layer in the application I will cover following important areas:
1. Caching at the service layer
2. Chunking (Creating different chunks for server and browser)
3. Adapters (Maitaining a common response format b/w providers for the clients)
4. Handling Error codes
5. Test cases
6. Switching b/w different service providers. How does client chooses the service provider?
7. How is the service layer integrated in the web application ?
Vijaya Krishna Kudva
Building high performance stack with React and PWA: the technology behind myntra web
A scalable stack
Micro apps Architecture benefits
Technology Choices and Performance
Few React Optimiztion tips
- Introduction to the talk
- Why is XSS bad anyways?
- I’ve Got No BeEF With You
- Demo of a real world account and browser compromise
- Going beyond it’s supposed application
- JS fuzzing engines
- Browser crashes and the $$$
- Server Side JS attacks
- The perils of insecure templating
- Server Side JS injection
- Remote Code Execution
- Client Side JS Attacks
- What’s that in my DOM?
- Case Study of
- Data Theft via a insecure Express app on a Desktop Client
- Breaking filters and Web Application Firewalls
- JS weirdness
- Twisted XSS payloads
- Case Study 1
- Case Study 2
- Session Hijacking using ActionScript and Flash
- Weaponising ActionScript for account takeovers
- Mutation XSS
- Abusing browsers’ code normalisation against them
- Stega whaa?
- Working with Alpha Channels in images
- Hidden in PlainSight
- Attacking NodeJS servers on exposed iOT devices
- What could go wrong you say!
- Closing notes
- The End / Q&A
Improving the performance of a React app: a case study
- How we measured our React App’s performance & improvement
- Performance metrics
- Test conditions
How we improved our React App’s performance
- Identified & removed unused libraries / part of libraries
- Code splitting with React’s lazy & suspense
- Identify & load specific libraries libraries dynamically
- Reduce babel transpiled code with babel-preset-env
Reduce download size with brotli-webpack-plugin
Details of Performance Improved
- Size of our JS Bundles
Breaking a monolithic front-end: HackerRank's case study
The need of breaking the monolithic frontend
- Reduce the app context.
- Separate deployment.
- Bottleneck for Innovation.
- Breaking the mololith app to multiple apps and modules.
- Modules as node packages.
- Keeping the code style uniform.
- Publishing Modules.
- Automate deployment for modules.
- Frontend Infra as a module.
Fine-tuning the workflow
- Better local development.
- Managing cross dependencies.
Leveraging web application vulnerabilities to build and open source intelligence arsenal (OSINT)
The talk will primarily focus on the prevalence of the following types of flaws:
overly permissive application programming interfaces business logic errors insecure direct object reference attacks use of insecure identifiers
Through providing real life examples of discovered issues, the talk will provide a starting point for where and how resourceful OSINT can be found and collected. Further, the talk will also touch upon how developers can avoid baking these issues into their services and products and how end users can avoid becoming a part of these databases. The talk will also cover targeting ‘hyper local’ service providers for the purpose of building categorised repositories.
Talk overview: Introduction: - What is OSINT? - Why build your own arsenal? - How can web application vulnerabilities help? - Minor case study on the uses of OSINT Scoping: - Targeting location-specific service providers - Usual suspects: What to look out for Numeric Identifiers, API(s), IDOR(s), Weak Auth; - Slides with examples Execution: “The good stuff” - Scraping the information, OR; - Creating tools to query information at will. Prevention: - As developers: What to avoid?; - As users: What to avoid? (protective techniques).
The Residency Towers, Coimbatore
1075, Avinashi Rd, P N Palayam,