This guide defines when to declare an incident, who is responsible for communication, and how to communicate externally during an incident.
It also defines how to act technically during an incident, emphasizing mitigation over fixes to reduce risk and downtime.
Note
Change the jdk.gz filename or folder name, based in your verion JDK downloaded as example I use the jdk-20.0.1
Preparing Artefacts
hi, i'm daniel. i'm a 15-year-old with some programming experience and i do a little bug hunting in my free time. here's the insane story of how I found a single bug that affected over half of all Fortune 500 companies:
If you've spent some time online, you’ve probably come across Zendesk.
Zendesk is a customer service tool used by some of the world’s top companies. It’s easy to set up: you link it to your company’s support email (like support@company.com), and Zendesk starts managing incoming emails and creating tickets. You can handle these tickets yourself or have a support team do it for you. Zendesk is a billion-dollar company, trusted by big names like Cloudflare.
Personally, I’ve always found it surprising that these massive companies, worth billions, rely on third-party tools like Zendesk instead of building their own in-house ticketing systems.
| /* eslint-disable react-hooks/rules-of-hooks */ | |
| // 24:33 error React Hook "useNextRouter" is called conditionally. React Hooks must be called in the exact same order in every component render react-hooks/rules-of-hooks | |
| // 25:43 error React Hook "useReactRouterNavigate" is called conditionally. React Hooks must be called in the exact same order in every component render react-hooks/rules-of-hooks | |
| // 43:35 error React Hook "useNextPathname" is called conditionally. React Hooks must be called in the exact same order in every component render react-hooks/rules-of-hooks | |
| // 44:37 error React Hook "useReactRouterLocation" is called conditionally. React Hooks must be called in the exact same order in every component render react-hooks/rules-of-hooks | |
| 'use client'; | |
| import { usePathname as useNextPathname, useRouter as useNextRouter } from 'next/navigation'; | |
| import { |
| // Migrate from eslint-plugin-import (no ESLint v9 support, multiple issues and missing features) | |
| // to eslint-plugin-import-x | |
| // | |
| // - https://www.npmjs.com/package/eslint-plugin-import | |
| // - https://www.npmjs.com/package/eslint-plugin-import-x | |
| // First, install `eslint-plugin-import-x` (and for TypeScript support, `@typescript-eslint/parser`) | |
| -import eslintImport from 'eslint-plugin-import'; | |
| +import eslintImportX from 'eslint-plugin-import-x'; |
| For the next 30 days, I decided to improve my pentesting skills. So, inspired in the challenge of #100DaysOfCode, i create the challenge #30DaysOfCTF. | |
| ## Main Rules: | |
| 1. Resolve a CTF challenge every day; | |
| 2. Create and publish a WriteUp about the CTF; | |
| 3. Share my progress and the WriteUp in the social midia with the hashtag #30DaysOfCTF. | |
| My #30DaysOfCTF starters in 05/13/2024. |
| function addSibs () { | |
| const div = document.createElement('div') | |
| const img = document.createElement('img') | |
| div.style.position = 'fixed' | |
| div.style.zIndex = '99999999' | |
| div.style.right = '100px' | |
| div.style.bottom = '0px' | |
| div.appendChild(img) |
| function addSibs () { | |
| const div = document.createElement('div') | |
| const img = document.createElement('img') | |
| div.style.position = 'fixed' | |
| div.style.zIndex = '99999999' | |
| div.style.right = '100px' | |
| div.style.bottom = '0px' | |
| div.appendChild(img) |