Responsible disclosure how to report a vulnerability the right way

Started by Cyberdyne, Today at 11:13 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Topic: Responsible disclosure how to report a vulnerability the right way   Views(Read 42 times)
Active members in this topic:
Cyberdyne(1)

Cyberdyne

TL;DR

  • Responsible or coordinated vulnerability disclosure means reporting a security flaw privately to the organisation that can fix it, giving them reasonable time, then sharing details publicly once users are protected
  • International standards ISO/IEC 29147 and ISO/IEC 30111 describe how organisations should receive and handle reports, and RFC 9116 defines the security.txt file that tells researchers where to report
  • A common norm is a 90 day disclosure deadline, popularised by Google Project Zero, with flexibility when vendors are actively working on fixes
  • Regulation now requires it: the UK PSTI regime requires connected product makers to publish a disclosure route, and the EU Cyber Resilience Act's vulnerability reporting duties began on 11 September 2026
  • Stay within legal and ethical limits: test only what you are authorised to test, avoid accessing personal data and follow published policies and safe harbour terms

Why disclosure matters

Every piece of software has bugs, and some of those bugs are security vulnerabilities. Researchers, students, customers and curious tinkerers find them all the time, sometimes deliberately and sometimes by accident. What happens next matters enormously. A flaw reported privately and fixed quickly protects users, while one sold to criminals or dumped publicly without warning can cause serious harm

Coordinated vulnerability disclosure, often called responsible disclosure, is the process that turns discoveries into fixes. The finder reports privately, the organisation investigates and builds a fix, and details become public once users can protect themselves. Done well, everyone benefits: users get safer products, organisations improve their security and researchers gain recognition. It is one of the quiet success stories of the security community

This thread explains how to report a vulnerability properly, what organisations should do in return and how laws and standards shape the process. It is written for both sides, because good disclosure depends on cooperation. Whether you have found a bug or are setting up a disclosure policy, the principles are the same. Respect, clarity and patience go a long way

Before you report: stay within the lines

The most important rule is to stay within legal and ethical boundaries. Only test systems you own or have permission to test, either through a published vulnerability disclosure policy, a bug bounty programme or explicit written authorisation. Many policies include safe harbour language promising not to pursue legal action against researchers who follow the rules. Read the policy carefully before you start

Avoid causing harm while testing. Do not access, modify or download personal data beyond the minimum needed to demonstrate the issue, do not disrupt services and do not use social engineering or physical intrusion unless explicitly permitted. If you stumble on sensitive data, stop, report what you found and delete any copies. Demonstrating that a flaw exists rarely requires exploiting it fully

Laws vary by country. In the US, the Department of Justice announced in May 2022 that it would not charge good faith security research under the federal Computer Fraud and Abuse Act, although civil risks and state laws still exist. In the UK, the Computer Misuse Act 1990 has no explicit defence for security research, and the government has been reviewing the Act since 2021 amid calls for reform. If in doubt, seek advice or report through a coordinator rather than testing further

Finding the right contact

Look first for a security.txt file. Defined in RFC 9116, published in April 2022, it is a simple text file placed at a standard location on a website, usually /.well-known/security.txt, listing how to report vulnerabilities and where to find the organisation's policy. Many organisations now publish one. It removes guesswork and ensures reports reach the right team

If there is no security.txt, check the website for a security, responsible disclosure or bug bounty page. Many companies run programmes through platforms such as HackerOne, Bugcrowd or Intigriti. For open source projects, look for a SECURITY.md file in the repository or a private vulnerability reporting feature on the code hosting platform. Avoid filing public issues for security bugs

If you cannot find a contact or the organisation does not respond, national coordinators can help. Computer emergency response teams such as CERT/CC in the US and national CSIRTs in Europe coordinate disclosure between researchers and vendors. Under the EU NIS2 Directive, member states designate CSIRTs as coordinators for vulnerability disclosure. The UK NCSC also offers guidance and a route for reports affecting government systems

Writing a good report

A good report is clear, reproducible and respectful. Describe the vulnerability, the affected product or URL and version, the steps to reproduce it and the potential impact. Include proof of concept code or screenshots if helpful, but avoid anything that exposes real user data. Suggest a fix if you have one, without making it a condition

Be explicit about your intentions and timeline. State that you are reporting in good faith, that you have not shared the details with others and when you would like to discuss public disclosure. Offer to answer questions. A courteous tone makes it far more likely that the organisation responds positively

Keep records of your communications. Note when you sent the report, who you contacted and what replies you received. These records help if disagreements arise later. They also make writing a public advisory easier once the issue is fixed

Timelines and public disclosure

How long should a vendor have before details go public? There is no universal answer, but a widely used norm is 90 days, popularised by Google's Project Zero research team. Project Zero's policy gives vendors 90 days to fix an issue, with a short additional period if a fix is released close to the deadline. Many researchers and organisations adopt similar timelines

Flexibility is sensible when vendors are communicating and making progress. Complex issues in hardware, firmware or widely deployed protocols may need longer, sometimes coordinated across many vendors at once. Conversely, if a vulnerability is being actively exploited, faster disclosure may protect users who need to apply mitigations. Good faith on both sides makes these judgement calls easier

When disclosure happens, aim to help defenders. A useful advisory explains the issue, affected versions, fixed versions and mitigations, and credits the finder if they wish. Many vulnerabilities receive a CVE identifier, a standard reference number assigned through the CVE Program. Publishing details responsibly helps other researchers learn and helps organisations prioritise patches

The CVE system

The Common Vulnerabilities and Exposures programme, launched in 1999 and operated by MITRE with US government funding, assigns identifiers to publicly disclosed vulnerabilities. Hundreds of CVE Numbering Authorities, including major vendors, open source foundations and coordinators, can assign identifiers within their scope. CVE numbers let everyone refer to the same flaw unambiguously. Vulnerability databases, scanners and patch tools rely on them

The programme faced a scare in April 2025, when MITRE warned that its funding contract was about to lapse. CISA extended the contract at the last minute, and the episode prompted wider discussion about the programme's governance and resilience, including the creation of a CVE Foundation by members of its board and the launch of ENISA's European Vulnerability Database. For researchers and organisations, the practical message is that CVE remains central, while complementary databases are growing. Watching how its governance evolves is worthwhile

What organisations should do

Organisations should make reporting easy and safe. Publish a vulnerability disclosure policy that explains how to report, what is in scope, what researchers can expect and what safe harbour you offer. Add a security.txt file and a monitored email address or form. The UK NCSC and CISA both provide templates and guidance for writing such policies

Respond promptly and professionally. Acknowledge reports quickly, ideally within a few working days, keep the reporter informed and agree timelines. Fix issues according to severity and credit researchers if they wish. ISO/IEC 29147 covers how to receive and disclose vulnerabilities, and ISO/IEC 30111 covers internal handling processes, giving organisations a solid framework

Avoid hostile reactions. Threatening legal action against good faith researchers damages reputation and discourages future reports, leaving vulnerabilities for criminals to find instead. Many organisations that once reacted badly now run successful bug bounty programmes. Treating researchers as partners pays off

Regulation is making disclosure mandatory

Disclosure is no longer only good practice. Since 29 April 2024, the UK's Product Security and Telecommunications Infrastructure regime has required manufacturers of consumer connectable products to publish a point of contact for reporting vulnerabilities and to explain how reports will be handled. Products without such a policy cannot legally be sold in the UK. This has pushed many device makers to set up disclosure processes for the first time

In the EU, the Cyber Resilience Act goes further. Since 11 September 2026, manufacturers of products with digital elements must report actively exploited vulnerabilities and severe security incidents through ENISA's Single Reporting Platform, with an early warning within 24 hours of becoming aware, a fuller notification within 72 hours and a final report later. Most other CRA obligations, including vulnerability handling requirements, apply from December 2027. Manufacturers must also have a coordinated disclosure policy

These rules make the researcher's report part of a regulated process. A well written report helps manufacturers meet their obligations quickly. Organisations without mature disclosure handling now face legal as well as reputational risk. Researchers benefit from clearer contact points and more predictable responses

Bug bounties

Bug bounty programmes reward researchers financially for valid vulnerability reports. Major technology companies, governments and many smaller organisations run them, often through platforms that handle triage and payment. Bounties can be a valuable income for skilled researchers and a cost effective security investment for organisations. They work best alongside, not instead of, internal security testing

Read bounty rules carefully. Scope, eligible vulnerability types, testing restrictions and disclosure rules vary widely, and some programmes require confidentiality even after fixes. If you want to publish your findings, check whether the programme allows it before participating. Clear expectations prevent disputes

A reporter's checklist

  • Test only within authorised scope and avoid harming users or services
  • Look for security.txt, a disclosure policy, SECURITY.md or a bug bounty page
  • Write a clear, reproducible report with impact and affected versions
  • Do not include or retain real user data beyond the minimum needed
  • Agree a disclosure timeline, commonly around 90 days, with flexibility for complex cases
  • Escalate to a national coordinator if you cannot reach the organisation
  • Keep records of all communications
  • Publish advisories that help defenders once users are protected

Closing thoughts

Responsible disclosure is a cornerstone of modern security. It channels curiosity and skill into fixes that protect millions of people, and it builds trust between researchers and the organisations they help. Standards, templates and now regulation make the process clearer than ever. Whether you are reporting your first bug or running a disclosure programme, the same principles of respect, clarity and patience apply

Please share your disclosure experiences in the replies, good and bad, with sensitive details removed. Advice for first time reporters and for small organisations setting up policies would be especially welcome. Together we can make reporting easier for everyone



Key references for citation

  • ISO/IEC 29147:2018 Vulnerability disclosure; ISO/IEC 30111:2019 Vulnerability handling processes
  • RFC 9116, A File Format to Aid in Security Vulnerability Disclosure (security.txt), April 2022
  • Google Project Zero, vulnerability disclosure policy
  • US Department of Justice, policy on charging under the Computer Fraud and Abuse Act, May 2022
  • UK PSTI regime, in force 29 April 2024
  • EU Cyber Resilience Act reporting obligations from 11 September 2026; ENISA Single Reporting Platform