Skip to main content
Be Bitwise

Reporting Your First Zero Day

Zero-Day Discovery Workflow · Zero-Day Research track

7 min read

In this module

The Complete Report

You've mapped the attack surface, triaged a crash to its root cause, built a reliable proof of concept, and minimised the input. Now you assemble everything into a report that lets the vendor understand, reproduce, and fix the vulnerability.

A professional vulnerability report isn't an email saying "your software crashes when I send this file." It's a structured document that demonstrates competence, saves the vendor time, and gets the issue fixed faster. The quality of your report is a direct multiplier on how seriously you're taken.

Your report should contain:

  1. Summary. One paragraph describing the vulnerability, the affected component, and the potential impact.
  2. Affected software and versions. Product name, version numbers, and platform.
  3. Root cause analysis. The vulnerability class (heap overflow, use-after-free, etc.), the specific code location if known, and the mechanism by which the flaw is triggered.
  4. Proof of concept. The minimal crashing input or script, build instructions, and the exact command to reproduce.
  5. Impact assessment. What an attacker can achieve - denial of service, information disclosure, code execution. Include a CVSS v4.0 score if possible.
  6. Suggested fix. If you have analysed the code enough to suggest a fix, include it. This is optional but appreciated.
  7. Your contact details. Name, email, and PGP key fingerprint.

Finding the Vendor's Security Contact

Before you write a single word, identify where to send the report. Using the wrong channel delays the fix and may expose the vulnerability to people who should not see it.

Check security.txt

The first place to look is /.well-known/security.txt on the vendor's domain (as defined by RFC 9116):

bash
$ curl -s https://example.com/.well-known/security.txt
Contact: mailto:security@example.com
Encryption: https://example.com/.well-known/pgp-key.txt
Policy: https://example.com/security/disclosure-policy

Check for a Bug Bounty Programme

Search the vendor's website for a security page, or check platforms like HackerOne and Bugcrowd. Bug bounty programmes provide clear submission channels and often guarantee a response within defined timeframes.

Check for a PSIRT

Large vendors operate a Product Security Incident Response Team (PSIRT). Companies like Microsoft, Apple, Google, and Cisco publish dedicated security contact pages with instructions for researchers.

Fallback Options

If you cannot find a direct security contact:

  • Try security@vendor.com - it is a widely used convention.
  • Contact a national CSIRT (like the UK NCSC or US CERT/CC) and ask them to coordinate.
  • For open-source projects, check the repository for a SECURITY.md file or a security policy in the project settings.
Never Use Public Channels

Do not report vulnerabilities through public bug trackers, social media, or general support channels. These expose the vulnerability to anyone monitoring those channels. Always use private, preferably encrypted, communication for initial reports. If no private channel exists, a national CSIRT can act as a trusted intermediary.

Encrypted Communication

Vulnerability details are sensitive. Intercepted in transit, they could be exploited before the vendor patches anything. Encrypt when you can — ideally always.

PGP/GPG

Most vendor security teams publish a PGP key for encrypted correspondence. The key is typically linked from their security page or security.txt file.

bash
# Import the vendor's public key
$ curl -s https://example.com/.well-known/pgp-key.txt | gpg --import
# Encrypt your report
$ gpg --encrypt --armor --recipient security@example.com report.txt
# The output file report.txt.asc can be sent via email

If the vendor does not publish a PGP key, mention in your initial (non-detailed) contact that you have a vulnerability to report and ask them to provide an encryption key or establish a secure channel. Many vendors use secure portals, encrypted email services, or invite researchers to a private issue tracker.

Initial Contact Template

Your first message should establish contact without revealing the full technical details:

c
Subject: Security vulnerability in [Product Name]
Hello,
I have discovered a security vulnerability in [Product Name]
that affects versions [X.Y.Z through A.B.C]. The issue is a
[vulnerability class, e.g., heap-based buffer overflow] in the
[component name] that could allow [brief impact statement,
e.g., remote code execution when processing crafted input].
I would like to share the full technical details, including
a proof of concept, through an encrypted channel. My PGP key
fingerprint is [your fingerprint].
Could you provide your preferred method for receiving the
complete report?
Regards,
[Your name]

Timeline Expectations

After submitting your report, set reasonable expectations for the response process:

StageTypical Timeframe
Initial acknowledgement1-5 business days
Triage and confirmation1-2 weeks
Patch development30-90 days (depends on complexity)
Coordinated disclosureAgreed date, typically at patch release
CVE assignmentApproximately 30 days if requested through MITRE

If the vendor is a CNA, they will typically assign a CVE ID during their triage process. If they are not a CNA, you may need to request one separately through cveform.mitre.org, as covered in Responsible Disclosure & UK Law: CVE Process.

What Happens After You Submit

The vendor's response process typically follows these stages:

  1. Acknowledgement. The vendor confirms they received your report and provides a tracking number or reference.
  2. Triage. The vendor's security team reproduces the issue and assesses its severity.
  3. Remediation. Engineers develop and test a fix. This may involve multiple rounds of patches and reviews.
  4. Coordination. The vendor contacts you to agree on a disclosure date, share the CVE ID, and review advisory content.
  5. Release. The vendor publishes the patch and an advisory on the agreed date.
  6. Public disclosure. You publish your own advisory, crediting the discovery and providing technical details.
Not Every Report Goes Smoothly

Some vendors respond within hours. Others take weeks to acknowledge a report and months to release a fix. Some dispute the severity, deny the vulnerability exists, or stop responding entirely. This is frustrating but not uncommon. Maintain professionalism throughout. Document every communication and stick to your agreed disclosure deadline. If the vendor has had reasonable time and has not acted, publication serves the public interest.

Following Up Professionally

If you do not receive an acknowledgement within a reasonable period (5-7 business days), send a polite follow-up:

c
Subject: Re: Security vulnerability in [Product Name] - follow up
Hello,
I wanted to follow up on my report submitted on [date]
regarding a [vulnerability class] in [Product Name]. I have
not yet received an acknowledgement.
Could you confirm that the report was received? I am happy
to re-send the details if needed or to use an alternative
communication channel.
Regards,
[Your name]

If repeated follow-ups go unanswered over several weeks, consider escalating through a national CSIRT or CERT/CC. They have established relationships with vendors and can often facilitate communication where direct contact has failed.

The Researcher's Checklist

Before submitting, verify:

  • The vulnerability is real and reproducible
  • The PoC is minimised to the smallest trigger
  • The report includes all necessary information (versions, steps, impact)
  • You have identified the correct security contact
  • The report is encrypted or sent through a secure channel
  • You have documented your own timeline (discovery date, contact date)
  • You have set a clear disclosure deadline in your initial communication
  • You have not disclosed details publicly before contacting the vendor

Submitting your first real vulnerability report is a genuine milestone. You're no longer studying security — you're contributing to it. The process takes patience and persistence, and it won't always go smoothly. But when a patch ships because of your work, that's a concrete improvement in the world.