Vulnerability research is the search for security flaws in software and hardware, and the work of explaining and reporting them so they get fixed. It combines code reading, testing and patience. Research your own code, open-source projects you run locally and programmes that invite testing, and follow each project's disclosure policy.
Key concepts
- Root cause: understand why the bug exists, not just how to trigger it; the cause tells you where else it hides.
- Bug classes: injection, memory corruption, logic errors, race conditions and broken access checks recur across software.
- Methods: code audit, targeted testing, fuzzing and static analysis, often combined.
- Triage and severity: judge reach, required access and impact, to rate the problem honestly.
- Coordinated disclosure: tell the maintainer privately, agree a timeline, and publish after a fix is available.
Vocabulary
- CVE: a public identifier for a vulnerability.
- CWE: a catalogue of weakness types.
- Advisory: the public notice describing a flaw, its impact and its fix.
- Bug bounty: a programme in which an organisation invites reports under stated rules.
What to study, in order
- Read code in one language fluently, then in C or a similar language where memory bugs live.
- Study published advisories: find the commit that fixed each, and explain the root cause in your own words.
- Audit a small open-source library locally with a checklist of bug classes, and take notes.
- Add a static analyser and a fuzzer to your own project, and fix what they find.
- Practise a full report: summary, affected versions, reproduction in a lab, impact and a suggested fix.
Related tags
#fuzzing #exploit-development #static-analysis #appsec #code-review