In this post, we’ll use the example of prototype pollution to walk through how the rule maintenance features of Snyk Code help developers and security professionals protect their application. We won’t explore prototype pollution in depth in this post, but if you’d like to learn more about it, I recommend taking this Snyk learn lesson or reading the above mentioned Hub article.
The traditional approach to maintaining rule sets
The quality of a static application security testing (SAST) tool — and more broadly, of static code analysis tools — is largely determined by the quality of its rule set. Simply put, the tool transforms the source code into a data structure and uses these rules to search for malicious patterns. In most modern scanners, rules are written in a somewhat uncommon style called logical programming.
Writing and maintaining rule sets is not an easy task. It requires intimate knowledge of logical programming, as well as the language and libraries being scanned. After the rules have been written, the process of debugging them creates another challenge. They must be tested on real code before being used in production, which can easily take hours. As a result, research1 has shown that developers seldom change the configuration. While there are some cases where custom rules make sense, in the majority of cases, the tool should simply work.
Note: There are some very limited cases where custom rules make sense (if you are such a case, let us know). In the majority of cases, the tool should “simply work” — no tinkering from the user-side necessary!
Snyk Code modernizes rule maintenance
Snyk Code has a different approach. We see the rule set as part of the product and do not ask our customers to maintain these rules to make the tool usable. In an industry that believes “custom rules” are a necessary capability of a SAST tool, Snyk offers a simplified solution to its users. Our security experts take responsibility to build and maintain the rule set using the powerful and fast engine on huge numbers of open source projects as test and training set. Snyk’s “humans-in-the-loop” constantly monitor and oversee the results, and act as quality control so the customers do not have to.
One of the Snyk engineers working on rule maintenance is Alessio Della Libera, a security researcher who joined Snyk roughly a year ago. When asked about Snyk Code’s unique approach, he described it as “[…] a kind of loop. Start changing something and checking the changes against the results from the data set takes a few minutes. Being able to iterate so fast is super helpful.”
The training set of open source projects are constantly monitored and updated according to scan findings and feedback from users. During this monitoring, Libera became aware that one of our existing rules did not behave according to our requirements.
After making changes to the rule and testing it, two results stood out. The open source project called appwrite.io contained a copy of the litespeed.js library. According to their website, “Appwrite is a self-hosted solution that provides developers with a set of easy-to-use and integrate REST APIs to manage their core backend needs”. Snyk Code reported the same issue on both the library via the marketplace and the project itself.
Informing the maintainers
After informing the project maintainers at Appwrite, they quickly released patches to cover the appwrite/server-ce package and litespeed.js package. Since the application is widely used, a CVE was also published in the National Vulnerability Database.
After the vulnerability had been resolved, the maintainers at Appwrite offered Libera a gift card, which he asked to have donated for the benefit of the open source community. All in all, we can only applaud Appwrite’s handling of the security issue. By taking it seriously and working with the community to solve the problem, they helped keep open source secure.
By constantly developing and maintaining the rule sets that power Snyk Code, Snyk ensures consistent growth in coverage accuracy. We make sure to constantly scan for new issue patterns and implement them while maintaining existing rules. To us, the rule set is part of the product — and our responsibility to build and maintain.
Try Snyk Code for free today, and see how our developer-centric security platform helps you write high quality code more efficiently than ever.
Snyk is the leader in developer security. We empower the world’s developers to build secure applications and equip security teams to meet the demands of the digital world. Our developer-first approach ensures organizations can secure all of the critical components of their applications from code to cloud, leading to increased developer productivity, revenue growth, customer satisfaction, cost savings and an overall improved security posture. Snyk’s Developer Security Platform automatically integrates with a developer’s workflow and is purpose-built for security teams to collaborate with their development teams. Snyk is used by 1,200 customers worldwide today, including industry leaders such as Asurion, Google, Intuit, MongoDB, New Relic, Revolut and Salesforce.
Snyk is recognized on the Forbes Cloud 100 2021, the 2021 CNBC Disruptor 50 and was named a Visionary in the 2021 Gartner Magic Quadrant for AST.
For more information, visit https://snyk.io.