4276 articles
4276 ARTICLES
Snyk’s goal is to help you use open source in a secure way. Vulnerabilities are one indicator that a dependency is unhealthy, but there are other risk factors at play as well. For that reason, we have a whole team working on making Snyk the go-to destination for information about your dependencies – from Security to License information, and now to Health.
One of FIRST’s initiatives is a Special Interest Group (SIG) that is responsible for developing and maintaining the Common Vulnerability Scoring System (CVSS) specification in an effort to help teams understand and prioritize the severity of a security vulnerability.
This post discusses the CRLF injection vulnerability recently discovered in a popular Python library and provides guidance on how you can protect your Python project.
We’re launching a new JVM Ecosystem Survey for 2019. The goal of this survey is to understand the lay of the land across the entire JVM ecosystem, and Java in particular.
Mismanaging the configuration of your Amazon S3 resources can lead to significant security and compliance incidents. Learn how to prevent these risks.
Affected versions of axios are vulnerable to Denial of Service (DoS) because content continues to be processed from requests even after maxContentLength is exceeded, causing increased I/O and CPU usage.
This post outlines Snyk’s 8 security best practices for working with Azure Repos.
Having team-wide rules that prevent credentials from being stored as code is a great way to police bad actions in your existing developer workflow.
If you find sensitive data in your Azure Repos repository, you need to do several things to recover, including invalidating the tokens and passwords that were once public.
Adding a SECURITY.md file to your Azure Repos helps your users find the information they need and encourages maintainers to consider general security practices.
By adding Snyk’s native integration with Azure Repos, each pull request will be tested to ensure new vulnerabilities aren’t introduced into the code base. Policies can be defined to configure the severity level of a vulnerability that fails the merge. The following image displays a failed PR due to new vulnerabilities that it would have added:
