Skip to main content
Be Bitwise

Responsible Disclosure & CVEs

Exploit Development & Real-World Impact · Exploit Development track

4 min read

In this module

The Ethics of Breaking Things

Discovering a vulnerability is a strange moment. You know about a flaw that could affect millions of users, and right now only you know. What you do next matters enormously — the security community has developed norms specifically to handle this tension between transparency and protection.

Responsible (Coordinated) Disclosure

The most widely accepted approach follows these steps:

  1. Discover - the researcher finds the vulnerability through fuzzing, code review, or reverse engineering.
  2. Notify the vendor privately - contact the affected software vendor with a detailed report of the vulnerability, how to reproduce it, and its potential impact. Do not publish the details yet.
  3. Vendor develops a patch - the vendor analyses the report and creates a fix. A common deadline is 90 days from initial notification.
  4. Public disclosure - once the patch is available (or the deadline expires), the vulnerability details are published so the community can verify the fix and learn from the bug.

This process protects users by giving the vendor time to fix the issue before attackers learn how to exploit it.

The 90-Day Standard

Google's Project Zero popularised the 90-day disclosure deadline: if a vendor hasn't released a patch within 90 days of private notification, the details are published regardless. From 2021 it used a "90+30" model, holding back details of a fixed bug until 30 days after the patch so users had time to update. In November 2026 it went further. Its "Full X" policy publishes details X days after the report whether or not a fix has shipped, with no grace period: 90 days now, 60 from February 2027 and 30 from January 2028. Its reasoning is that AI tools let attackers find bugs, and reverse a patch, far faster than before. Whatever the exact number, the fixed deadline is what stops vendors sitting on reports indefinitely while users stay exposed.

Here's what a well-behaved 90-day case looks like from start to finish. Click through the events and note who's acting at each point: most of the middle belongs to the vendor, and the researcher's main job there is to stay reachable.

Researcher
Vendor
Public
Coordinator
Day 0Day 30Day 60Day 90Day 120

Click a step to see details about the coordinated disclosure process

The CVE System

Common Vulnerabilities and Exposures (CVE) is a standardised system for identifying publicly known vulnerabilities. Each entry gets a unique identifier like CVE-2024-1234. The CVE system allows everyone - researchers, vendors, system administrators, security tools - to reference the same vulnerability unambiguously.

A CVE record includes a unique ID, description, affected software and versions, and references to patches and advisories. Severity scores are usually layered on top: NVD adds a CVSS score, and the CNA that assigned the ID may supply its own. Concise by design — the point is interoperability, not depth.

Bug Bounty Programs

Many organisations now pay researchers for responsibly disclosed vulnerabilities. Bug bounty programs create a legitimate, incentivized path for reporting bugs. Payouts range from a few hundred dollars for minor issues to hundreds of thousands for critical vulnerabilities in major platforms.

These programs give independent researchers a legitimate outlet — and pay — instead of pushing them towards underground exploit markets. Google, Microsoft, and Apple run big in-house programs; HackerOne and Bugcrowd host programs for thousands of smaller organisations.

Security research exists in a complex legal environment. Laws like the Computer Fraud and Abuse Act (CFAA) in the United States can criminalize even well-intentioned research if it involves accessing systems without authorisation. Researchers must understand the legal boundaries: test only on systems you own or have explicit permission to test, follow responsible disclosure practices, and consider consulting legal counsel before testing third-party systems.

Defensive Thinking

If you discover a vulnerability, follow responsible disclosure. Report the bug, give the vendor a reasonable window, and contribute to making software safer. The knowledge you've built in these modules is a genuinely powerful tool — treat it accordingly.