Cover of the book Symfony 5: The Fast Track

Symfony 5: The Fast Track is the best book to learn modern Symfony development, from zero to production. +300 pages showcasing Symfony with Docker, APIs, queues & async tasks, Webpack, SPAs, etc.

  1. Home
  2. Documentation
  3. Security
  4. How to Check for Known Security Vulnerabilities in Your Dependencies
WARNING: You are browsing the documentation for Symfony 3.2 which is not maintained anymore. Consider upgrading your projects to Symfony 5.1.

How to Check for Known Security Vulnerabilities in Your Dependencies

3.2 version
Unmaintained
2.7 2.8 3.0 3.1 3.2 3.3 3.4 4.0 4.1

How to Check for Known Security Vulnerabilities in Your Dependencies

When using lots of dependencies in your Symfony projects, some of them may contain security vulnerabilities. That’s why Symfony includes a command called security:check that checks your composer.lock file to find any known security vulnerability in your installed dependencies:

1
$ php bin/console security:check

A good security practice is to execute this command regularly to be able to update or replace compromised dependencies as soon as possible. Internally, this command uses the public security advisories database published by the FriendsOfPHP organization.

Tip

The security:check command terminates with a non-zero exit code if any of your dependencies is affected by a known security vulnerability. Therefore, you can easily integrate it in your build process.

Note

To enable the security:check command, make sure the SensioDistributionBundle is installed and enabled in your application.

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.