This is a summary of the Terms of Use. To read the full terms, scroll down or click here.
Terms of Use
Disclaimer: This summary is not a part of the Terms of Use and is not a legal document.
It is simply a handy reference for understanding the full terms. Think of it as the
user-friendly interface to the legal language of our Terms of Use.
Part of our mission is to:
|
This is not an officially supported Google product.
Welcome to Vulncode-DB! Vulncode-DB, is a nonprofit project whose mission is to empower and engage people around the world to collect and develop content around security vulnerabilities under a free license or in the public domain, and to disseminate it effectively and globally, free of charge.
We provide the essential infrastructure and organizational framework for the development of content around vulnerabilities and other endeavors which serve this mission. We strive to make and keep educational and informational content from the project available on the internet free of charge, in perpetuity.
We welcome you (“you” or the “user”) as a reader, editor, author, or contributor of the Vulncode-DB project, and we encourage you to join the Vulncode-DB community. Before you participate, however, we ask that you please read and agree to the following Terms of Use (“Terms of Use”).
These Terms of Use tell you about our public services at Vulncode-DB, our relationship to you as a user, and the rights and responsibilities that guide us both. We want you to know that we host an incredible quantity of educational and informational content, all of which is contributed and made possible by users like yourself. Generally we do not contribute, monitor, or delete content (with the rare exception of policies like these Terms of Use or legal compliance for DMCA notices). This means that editorial control is in the hands of you and your fellow users who create and manage the content. We merely host this content.
The community – the network of users who are constantly building and providing various project entries – are the principal means through which the goals of the mission are achieved. The community contributes to and helps govern our sites.
Please be aware that you are legally responsible for all of your contributions, edits, and re-use of Vulncode-DB content under the laws where you live or where you view or edit content. This means it is important that you use caution when posting content. In light of this responsibility, we have some rules about what you cannot post, most of which is either for your own protection or for the protection of other users like yourself. Please keep in mind that the content we host is for general informational purposes only, so if you need expert advice for a particular security issue you should seek the help of a licensed or qualified professional. We also include other important notices and disclaimers, so please read these Terms of Use in their entirety.
Vulncode-DB is dedicated to encouraging the growth, development and distribution of free information security related content for the public free of charge. Our role is to host some of the largest collaboratively edited data about vulnerabilities. However, we act only as a hosting service, maintaining the infrastructure and organizational framework that allows our users to build Vulncode-DB by contributing and editing content themselves. Because of our unique role, there are a couple of things you should be aware of when considering our relationship to you, the project, and the other users:
Vulncode-DB aims to store as little data as necessary about you to provide its service. For this reason, we provide access to the platform exclusively through third-party identity providers such as Google and ask for a minimum set of information such as the name, email and profile picture to be shared with Vulncode-DB. Because our services are used by people all over the world, personal information that we collect may be stored and processed in the United States of America or any other country in which we or our agents maintain facilities. By using our services, you consent to any such transfer of information outside your country.
The Vulncode-DB project only exists because of the vibrant community of users like you who collaborate to write, edit, and curate the content. We happily welcome your participation in this community. We encourage you to be civil and polite in your interactions with others in the community, to act in good faith, and to make edits and contributions aimed at furthering the mission of the shared project.
Certain activities, whether legal or illegal, may be harmful to other users and violate our rules, and some activities may also subject you to liability. Therefore, for your own protection and for that of other users, you may not engage in such activities on our sites. These activities include:
We reserve the right to exercise our enforcement discretion with respect to the above terms.
You are responsible for safeguarding your account and should never disclose access to it to any third party.
To grow the commons of free knowledge and free culture, all users contributing to the project are required to grant broad permissions to the general public to re-distribute and re-use their contributions freely, so long as that use is properly attributed and the same freedom to re-use and re-distribute is granted to any derivative works. In keeping with our goal of providing free information to the widest possible audience, we require that when necessary all submitted content be licensed so that it is freely reusable by anyone who cares to access it.
You agree to the following licensing requirements:
(Re-users may comply with either license or both.)
Please note that these licenses do allow commercial uses of your contributions, as long as such uses are compliant with the terms.
You agree that, if you import text under a CC BY-SA license that requires attribution, you must credit the author(s) in a reasonable fashion. The attribution requirements are sometimes too intrusive for particular circumstances (regardless of the license), and there may be instances where the Vulncode-DB community decides that imported text cannot be used for that reason.
When you re-use or re-distribute a text page developed by the Vulncode-DB community, you agree to attribute the authors in any of the following fashions:
If the text content was imported from another source, it is possible that the content is licensed under a compatible CC BY-SA license but not GFDL (as described in “Importing text,” above). In that case, you agree to comply with the compatible CC BY-SA license and do not have the option to re-license it under GFDL. To determine the license that applies to the content that you seek to re-use or re-distribute, you should review the page footer, page history, and discussion page.
In addition, please be aware that text that originated from external sources such as NVD/CVE and was imported into the project may be under a license that attaches additional attribution requirements. Users agree to indicate these additional attribution requirements clearly. Such requirements are indicated in this Terms of Use.
Vulncode-DB wants to ensure that the content that we host can be re-used by other users without fear of liability and that it is not infringing the proprietary rights of others. In fairness to our users, as well as to other creators and copyright holders, our policy is to respond to notices of alleged infringement that comply with the formalities of the Digital Millennium Copyright Act (DMCA). Pursuant to the DMCA, we will terminate, in appropriate circumstances, users and account holders of our system and network who are repeat infringers.
However, we also recognize that not every takedown notice is valid or in good faith. In such cases, we strongly encourage users to file counter-notifications when they appropriately believe a DMCA takedown demand is invalid or improper. For more information on what to do if you think a DMCA notice has been improperly filed, you may wish to consult the Chilling Effects website.
If you are the owner of content that is being improperly used on one of the project without your permission, you may request that the content be removed under the DMCA. To make such a request, please email us at rhabalovgmail.com.
This project builds upon data provided by the CVE and NVD data sets.
The CVE® is maintained by the Mitre Corporation. Please see the Mitre CVE®'s Terms of use:
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive,
no-charge, royalty-free, irrevocable copyright license to reproduce, prepare
derivative works of, publicly display, publicly perform, sublicense, and
distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for
such purposes is authorized provided that you reproduce MITRE's copyright
designation and this license in any such copy.
The National Vulnerability Database is maintained by the U.S. government. Please see the NVD's FAQ:
All NVD data is freely available from our XML Data Feeds. There are no fees,
licensing restrictions, or even a requirement to register. All NIST
publications are available in the public domain according to Title 17 of the
United States Code. Acknowledgment of the NVD when using our information is
appreciated. In addition, please email nvd@nist.gov to let us know how the
information is being used.
You are solely responsible for your use of any third-party websites or resources. Although the project contain links to third-party websites and resources, we do not endorse and are not responsible or liable for their availability, accuracy, or the related content, products, or services (including, without limitation, any viruses or other disabling features), nor do we have any obligation to monitor such third-party content.
The community has the primary role in creating and enforcing policies applying to Vulncode-DB. At Vulncode-DB, we rarely intervene in community decisions about policy and its enforcement. In an unusual case, the need may arise, or the community may ask us, to address an especially problematic user because of significant project disturbance or dangerous behavior. In such cases, we reserve the right, but do not have the obligation to:
In the interests of our users and the project, in the extreme circumstance that any individual has had his or her account or access blocked under this provision, they are prohibited from creating or using another account on or seeking access to the project, unless we provide explicit permission. Without limiting the authority of the community, Vulncode-DB itself will not ban a user from editing or contributing or block a user's account or access solely because of good faith criticism that does not result in actions otherwise violating these Terms of Use or community policies.
The Vulncode-DB community and its members may also take action when so allowed by the community, including but not limited to warning, investigating, blocking, or banning users who violate those policies. You agree to comply with the final decisions of project administrators.
The blocking of an account or access or the banning of a user under this provision shall be in accordance with Section 8 of these Terms of Use.
Though we hope you will stay and continue to contribute to the project, you can stop using our services any time. In certain (hopefully unlikely) circumstances it may be necessary for either ourselves or the Vulncode-DB community or its members to terminate part or all of our services, terminate these Terms of Use, block your account or access, or ban you as a user. If your account or access is blocked or otherwise terminated for any reason, your public contributions will remain publicly available (subject to applicable policies), and, unless we notify you otherwise, you may still access our public pages for the sole purpose of reading publicly available content on the project. In such circumstances, however, you may not be able to access your account or settings. We reserve the right to suspend or end the services at any time, with or without cause, and with or without notice. Even after your use and participation are banned, blocked or otherwise suspended, these Terms of Use will remain in effect with respect to relevant provisions, including Sections 1, 3, 4, 6, 8-13, and 15.
Highlighted for emphasis
We hope that no serious disagreements arise involving you, but, in the event there is a dispute, we encourage you to seek resolution through the dispute resolution procedures or mechanisms provided by the project.
To ensure that disputes are dealt with soon after they arise, you agree that regardless of any statute or law to the contrary, any claim or cause of action you might have arising out of or related to use of our services or these Terms of Use must be filed within the applicable statute of limitations or, if earlier, one (1) year after the pertinent facts underlying such claim or cause of action could have been discovered with reasonable diligence (or be forever barred).
Highlighted for emphasis
At Vulncode-DB, we do our best to provide educational and informational content to a very wide audience, but your use of our services is at your sole risk. We provide these services on an "as is" and "as available" basis, and we expressly disclaim all express or implied warranties of all kinds, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, and non-infringement. We make no warranty that our services will meet your requirements, be safe, secure, uninterrupted, timely, accurate, or error-free, or that your information will be secure.
We are not responsible for the content, data, or actions of third parties, and you release us from any claims and damages, known and unknown, arising out of or in any way connected with any claim you have against any such third parties. No advice or information, whether oral or written, obtained by you from us or through or from our services creates any warranty not expressly stated in these Terms of Use.
Any material downloaded or otherwise obtained through your use of our services is done at your own discretion and risk, and you will be solely responsible for any damage to your computer system or loss of data that results from the download of any such material. You agree that we have no responsibility or liability for the deletion of, or the failure to store or to transmit, any content or communication maintained by the service. We retain the right to create limits on use and storage at our sole discretion at any time with or without notice.
Some states or jurisdictions do not allow the types of disclaimers in this section, so they may not apply to you either in part or in full depending on the law.
Highlighted for emphasis
Vulncode-DB will not be liable to you or to any other party for any direct, indirect, incidental, special, consequential or exemplary damages, including but not limited to, damages for loss of profits, goodwill, use, data, or other intangible losses, regardless of whether we were advised of the possibility of such damage. In no event shall our liability exceed one thousand U.S. dollars (USD 1000.00) in aggregate. In the case that applicable law may not allow the limitation or exclusion of liability or incidental or consequential damages, the above limitation or exclusion may not apply to you, although our liability will be limited to the fullest extent permitted by applicable law.Just as the Vulncode-DB community's input is essential for the growth and maintenance of the project, we believe that community input is essential for these Terms of Use to properly serve our users. It is also essential for a fair contract. Therefore, we will provide these Terms of Use, as well as any substantial future revisions of these Terms of Use, to the community for modification via the project's GitHub repository.
We ask that you please periodically review the most up-to-date version of these Terms of Use. Your continued use of our services after the new Terms of Use become official following the notice and review period constitutes an acceptance of these Terms of Use on your part. For the protection of Vulncode-DB and other users like yourself, if you do not agree with our Terms of Use, you cannot use our services.
These Terms of Use do not create an employment, agency, partnership, or joint venture relationship between you and us, Vulncode-DB. If you have not signed a separate agreement with us, these Terms of Use are the entire agreement between you and us. If there is any conflict between these Terms of Use and a signed written agreement between you and us, the signed agreement will control.
You agree that we may provide you with notices, including those regarding changes to the Terms of Use, by email, regular mail, or postings on project websites.
If in any circumstance, we do not apply or enforce any provision of these Terms of Use, it is not a waiver of that provision.
You understand that, unless otherwise agreed to in writing by us, you have no expectation of compensation for any activity, contribution, or idea that you provide to us, the community, or the Vulncode-DB project.
Notwithstanding any provision to the contrary in these Terms of Use, we (Vulncode-DB) and you agree not to modify the applicable terms and requirements of any free license that is employed on the project or project editions when such free license is authorized by these Terms of Use.
These Terms of Use were written in English (U.S.). While we hope that translations of these Terms of Use are accurate, in the event of any differences in meaning between the original English version and a translation, the original English version takes precedence.
If any provision or part of a provision of these Terms of Use is found unlawful, void, or unenforceable, that provision or part of the provision is deemed severable from these Terms of Use and will be enforced to the maximum extent permissible, and all other provisions of these Terms of Use will remain in full force and effect.
We appreciate your taking the time to read these Terms of Use, and we are very happy to have you contributing to the project and using our services. Through your contributions, you are helping to build something really big – not only an important collection of collaboratively edited reference project that provides education and information to millions who might otherwise lack access, but also a vibrant community of like-minded and engaged peers, focused on a very noble goal.