Vulnerability disclosure meaning, in plain words

Vulnerability disclosure is reporting a hole to a product's maker, then publishing it. How IPA and JPCERT/CC coordinate it in Japan, and what security.txt does.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

Vulnerability disclosure is the process of reporting a hole you found to the maker of the product and then publishing it. In Japan, IPA receives reports of vulnerability-related information, and JPCERT/CC handles contact with product developers and the coordination of publication. This is a framework based on a notice of the Ministry of Economy, Trade and Industry, and according to IPA's page it has operated since July 8, 2004.

How does vulnerability disclosure work?

It can be compared to someone who notices a defect in a keyhole, tells the lock's manufacturer privately first, and tells everyone only after the fix is ready. Before publication, JPCERT/CC contacts the product developer and asks for a fix program or a workaround to be prepared. It also works with overseas organizations to coordinate a date for publishing worldwide at the same time.

If information is published, or leaks to a malicious third party, before a countermeasure is ready, attack code may be made and attacks may begin. For a vulnerability that affects several products, it is also important that the parties move in step. JPCERT/CC explains that publishing alone ahead of the coordinated date may put the users of other companies' products at risk.

IPA states that it does not force secrecy, force developers to take countermeasures, or force website operators to fix anything, so there is no guarantee that the response will be as expected. Reports are of two kinds: vulnerabilities in software products, and vulnerabilities in web applications. A contact point for reports can be set up with help from a free consultation.

Why does vulnerability disclosure matter?

The operator of a site may be on the receiving end of a message from an outsider about a vulnerability in the site. IPA asks product developers and website operators, when they receive a notice, to respond in line with the Information Security Early Warning Partnership guidelines. If there is no contact point to receive reports, the message does not arrive and the fix is delayed.

As a way of showing contact details in a machine-readable form, the IETF's RFC 9116 defines a format called security.txt. RFC 9116 says that researchers sometimes find a vulnerability but cannot find where to report it, and it stays unreported. If you prepare a contact point on the site you run, it becomes easier to receive reports from third parties.

Related terms

  • JVN: a site that publishes vulnerability information on products used in Japan.
  • JPCERT/CC: a coordination body that supports the response to security incidents in Japan.
  • IPA: a Japanese public body that promotes information security awareness.
  • Bug bounty: a program that pays a reward to people who find vulnerabilities.
  • Act on the Prohibition of Unauthorized Computer Access: a Japanese law that prohibits entering someone else's system without permission.

Next step

Check whether your site has a contact point through which outsiders can tell you about a vulnerability. To set one up, contact us. The free URL check shows what a visitor can see of your public site.

Frequently asked questions

If we find a vulnerability, may we publish it right away?

Please wait to publish. JPCERT/CC explains that if information is published before a countermeasure is ready, attacks may begin. The basic practice is to tell the product's developer or the site's operator first, and publish on the date that has been coordinated.

May we investigate the vulnerabilities of someone else's site without permission?

Please do not. Depending on how you came to find it, legal problems may arise. Also read the glossary entry on the Act on the Prohibition of Unauthorized Computer Access, and consult a specialist if you have doubts.

Frequently asked questions

If we find a vulnerability, may we publish it right away?

Please wait to publish. JPCERT/CC explains that if information is published before a countermeasure is ready, attacks may begin. The basic practice is to tell the product's developer or the site's operator first, and publish on the date that has been coordinated.

May we investigate the vulnerabilities of someone else's site without permission?

Please do not. Depending on how you came to find it, legal problems may arise. Also read the glossary entry on the Act on the Prohibition of Unauthorized Computer Access, and consult a specialist if you have doubts.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.