To get a trial key
fill out the form below
Team License (standard version)
Enterprise License (extended version)
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Request our prices
New License
License Renewal
--Select currency--
USD
EUR
GBP
RUB
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Message submitted.

Your message has been sent. We will email you at


If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

>
>
>
Zero-day Vulnerability

Zero-day Vulnerability

Jul 19 2021

A zero-day (also known as 0-day) vulnerability refers to the vulnerabilities that haven't been patched yet.

There may be holes and flaws in a software made by developers, who haven't detected these vulnerabilities and who haven't been informed about them yet. As long as vulnerability is not fixed, it can be used for network access, remote control access, data manipulation, etc.

The term "zero-day" reflects that developers don't have a single day to fix the defect, since it's unknown to them yet.

Most vulnerabilities are ordinary bugs in the application code, rather than flaws in security systems or high-level errors in logic.

The National Institute of Standards and Technology (NIST) reports that 64% of software vulnerabilities stem from programming errors and not a lack of security features.

There are so many ways to make an error in code that will cause a vulnerability. Luckily, there are certain patterns in all that. Most errors can be classified, and specific error patterns can be identified.

These patterns are well-studied and classified. The most significant classifications are:

Static code analyzers, such as PVS-Studio, are used to identify zero-day vulnerabilities. Usually, such analyzers support one or more of the standards listed above.

Note. Static analyzers are a fairly general concept. To emphasize that the analyzer is focused on preventing vulnerabilities, it is called a Static Application Security Testing (SAST) tool. See also PVS-Studio SAST.

It's not right to say that SAST solutions directly identify a zero-day vulnerability. Analyzers identify potential vulnerabilities. In other words, they indicate strange / abnormal code fragments that could be errors and security defects.

It's only a small part of the identified errors that pose a threat. Let's take, for example, a "buffer overflow" error. All standards classify this error as extremely dangerous from the security point of view. But only a small part of such errors can be exploited. Most of them cause a lot of troubles, but not fatal consequences. For example, a buffer overflow can cause an image corruption.

Only a part of the errors can cause vulnerabilities though, it makes no sense for programmers to try to separate them somehow. It would be rational to correct all the code sections with issued warnings (except obvious false positives of the analyzer). Even if it's not a potential vulnerability that is being fixed, but just a bug, it is still useful. Especially since it's often very difficult to understand whether one or another error poses a threat from the security point of view. It's better to play safe and fix it.

Additional links:

Popular related articles
PVS-Studio for Java

Date: Jan 17 2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…
The Evil within the Comparison Functions

Date: May 19 2017

Author: Andrey Karpov

Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: Oct 22 2018

Author: Andrey Karpov

Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…
Appreciate Static Code Analysis!

Date: Oct 16 2017

Author: Andrey Karpov

I am really astonished by the capabilities of static code analysis even though I am one of the developers of PVS-Studio analyzer myself. The tool surprised me the other day as it turned out to be sma…
The Last Line Effect

Date: May 31 2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: Jul 31 2017

Author: Andrey Karpov

After I wrote quite a big article about the analysis of the Tizen OS code, I received a large number of questions concerning the percentage of false positives and the density of errors (how many erro…
The way static analyzers fight against false positives, and why they do it

Date: Mar 20 2017

Author: Andrey Karpov

In my previous article I wrote that I don't like the approach of evaluating the efficiency of static analyzers with the help of synthetic tests. In that article, I give the example of a code fragment…
PVS-Studio ROI

Date: Jan 30 2019

Author: Andrey Karpov

Occasionally, we're asked a question, what monetary value the company will receive from using PVS-Studio. We decided to draw up a response in the form of an article and provide tables, which will sho…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 21 2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…
Free PVS-Studio for those who develops open source projects

Date: Dec 22 2018

Author: Andrey Karpov

On the New 2019 year's eve, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub, GitLab or Bitbucket. They are given free usage of PVS-Studio s…

Comments (0)

Next comments

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site.
Learn More →
Accept