Our website uses cookies to enhance your browsing experience.
Accept
to the top
close form

Fill out the form in 2 simple steps below:

Your contact information:

Step 1
Congratulations! This is your promo code!

Desired license type:

Step 2
Team license
Enterprise license
** By clicking this button you agree to our Privacy Policy statement
close form
Request our prices
New License
License Renewal
--Select currency--
USD
EUR
* By clicking this button you agree to our Privacy Policy statement

close form
Free PVS‑Studio license for Microsoft MVP specialists
* By clicking this button you agree to our Privacy Policy statement

close form
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

close form
I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

close form
check circle
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.

>
>
SCA (software composition analysis) wit…

SCA (software composition analysis) with PVS-Studio

PVS-Studio not only searches for weaknesses in code, but also searches for vulnerable components used in an application. Why does the analyzer do that?

Danger in vulnerable components

Modern applications often use third-party components, some of which have security weaknesses. If an application uses a vulnerable component, it can also become vulnerable to malicious attacks. Therefore, companies risk their reputation and finances.

The OWASP Top 10 2021 has a separate category for using vulnerable and outdated components: A06:2021 – Vulnerable and Outdated Components.

sca/image1.png

Is it possible to automatically check that the application doesn't use components with known vulnerabilities? Yes. To do this, specialized tools perform software composition analysis (SCA).

SCA tools inspect what components the application consists of. If they find vulnerable components, they notify the developers. After that the developers can update/replace the component, or protect the application in other ways.

PVS-Studio as SCA solution

As of now, PVS-Studio performs software composition analysis only in C# projects. Do you want to have the same feature for projects in C, C++, or Java? Let us know.

PVS-Studio analyzes a project and determines which components it uses. If the analyzer finds a vulnerable one — it issues a warning. This warning contains the name and version of a dangerous component, description of a vulnerability, and CVE-ID.

sca/image2.png

The V5625 diagnostic rule analyzes software components. The documentation describes how to work with the SCA warnings and fine-tune them for a specific project.