Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
JVN is a site that publishes vulnerability information on products used in Japan. Its formal name is Japan Vulnerability Notes. According to the JVN explanation, its purpose is to provide vulnerability-related information and countermeasure information on software and other products used in Japan, so that it can help with information security measures. JPCERT/CC and IPA run it jointly.
How does JVN work?
It can be compared to a bulletin board that collects notices of product recalls and repairs. What appears on JVN is the product and version in which a vulnerability was confirmed, details and analysis of the vulnerability, and links to the countermeasures and related information issued by the product's developer. Besides a fix program, a workaround may also be listed as a countermeasure.
The information published was reported and coordinated under the framework of the "Information Security Early Warning Partnership". Information coordinated with overseas coordination bodies is also published. In JPCERT/CC's explanation, the roles are divided like this: IPA receives the reports, JPCERT/CC coordinates with developers, and JVN is where the information is published.
If information is published or leaks before a countermeasure is ready, exploitation may begin, so the parties concerned align the date of publication. Check regularly whether the names of the products your company uses appear. For one look at the outside of your own site, the free URL check reads the page you enter.
Why does JVN matter?
Vulnerabilities in the CMS and plugins you use are a weak point that is easily left unnoticed. JVN is one place where you can look up, in Japanese, information on products used in Japan. From what is listed, you can judge whether your product and version are affected and decide the order of updates.
However, JVN covers software and other products used in Japan, so for products that are not listed, look in other sources too. Read it together with CVE, the worldwide identifier, and CVSS, the severity score, and it becomes easier to set priorities.
Related terms
- CVE: a worldwide identifier assigned to a vulnerability.
- CVSS: an index that shows the severity of a vulnerability as a score from 0 to 10.
- Vulnerability management: the effort to find holes in systems, set an order, and keep fixing them.
- Patch management: the effort to apply product updates without missing any.
- NVD: a US database that collects vulnerability information.
- JPCERT/CC: a coordination body that supports the response to security incidents in Japan.
Next step
Start by listing the names and versions of the CMS, plugins and server products your company uses. If a listed vulnerability affects you, contact us about the response. The free URL check reads what the page you enter exposes, including software names in headers.
Frequently asked questions
If we use a product listed on JVN, will we suffer damage right away?
Being listed does not itself mean damage. Check whether your product and version are affected and whether a countermeasure is available, and apply it if an update or other countermeasure has been issued. Also look at the severity and whether it is being exploited.
Can we post a vulnerability we found directly on JVN?
Listing on JVN goes through reporting and coordination under the Information Security Early Warning Partnership framework. IPA is the contact point for reports, and JPCERT/CC handles the coordination.
Frequently asked questions
If we use a product listed on JVN, will we suffer damage right away?
Being listed does not itself mean damage. Check whether your product and version are affected and whether a countermeasure is available, and apply it if an update or other countermeasure has been issued. Also look at the severity and whether it is being exploited.
Can we post a vulnerability we found directly on JVN?
Listing on JVN goes through reporting and coordination under the Information Security Early Warning Partnership framework. IPA is the contact point for reports, and JPCERT/CC handles the coordination.