CVE-2017-16020: Unsafe eval() in summit

summit Updated 02 Oct 2025

Summary

01/09/2020
No i
Critical
9.8

CVE-2017-16020: Unsafe eval() in summit allows arbitrary code execution. Affects summit versions >= 0.1.0, <= 0.1.22. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The summit package is an npm package used for a specific purpose. It is vulnerable to an unsafe eval() function call when using the PouchDB driver. This vulnerability allows attackers to execute arbitrary commands by exploiting collection names. The package author has abandoned this feature entirely.

Vulnerability Detail

The vulnerability in summit arises from the usage of the eval() function, which can execute arbitrary code. Attackers can exploit this vulnerability by manipulating collection names when using the PouchDB driver. This can lead to the execution of unintended commands, potentially resulting in unauthorized access, data breaches, or other malicious activities.

How To Fix

No fixed version is published for this vulnerability.

Currently, there is no direct patch available for this vulnerability. The best way to mitigate the issue is to avoid using the PouchDB driver. It is recommended to explore alternative drivers or packages that do not rely on the vulnerable functionality. Additionally, it is crucial to keep the summit package up to date with the latest releases to benefit from any future security patches.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a workaround, developers can consider implementing input validation and sanitization techniques to ensure that collection names do not contain any malicious code. By carefully validating and filtering user input, the risk of exploitation can be reduced. However, this workaround may not provide complete protection and should be used in conjunction with other security measures.

Conclusion

The summit package is vulnerable to an unsafe eval() function call when using the PouchDB driver. To mitigate this vulnerability, it is advised to avoid using the vulnerable driver and keep the package up to date. Input validation can provide some protection, but it should be used in conjunction with other security measures. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for summit →

Share this vulnerability

FAQ

The vulnerability allows attackers to execute arbitrary commands, potentially leading to unauthorized access, data breaches, or other malicious activities.

No, there is no direct patch available at this time. The recommended approach is to avoid using the vulnerable PouchDB driver and keep the summit package up to date.

While input validation can help reduce the risk of exploitation, it may not provide complete protection. It is recommended to combine input validation with other security measures and avoid using the vulnerable functionality.

Yes, developers can explore alternative drivers or packages that do not rely on the vulnerable PouchDB driver. It is important to evaluate the security of these alternatives before implementation.

To stay updated on security patches, it is recommended to regularly check for new releases of the summit package and follow the official documentation or community channels for any security-related announcements.

How To Fix

No fixed version is published for this vulnerability.

Currently, there is no direct patch available for this vulnerability. The best way to mitigate the issue is to avoid using the PouchDB driver. It is recommended to explore alternative drivers or packages that do not rely on the vulnerable functionality. Additionally, it is crucial to keep the summit package up to date with the latest releases to benefit from any future security patches.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.