CVE-2018-3767: Denial of Service in memjs

memjs Updated 02 Oct 2025

Summary

10/10/2018
No i
Critical
9.1

CVE-2018-3767: Denial of Service in memjs. Affects memjs versions < 1.2.0. 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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The memjs package is an npm package that provides a JavaScript client for the Memcached caching system. It allows developers to interact with Memcached servers and perform caching operations in their applications. Memcached is a widely used distributed memory caching system that helps improve the performance of web applications by storing frequently accessed data in memory.

However, versions of memjs prior to 1.2.2 are vulnerable to a Denial of Service (DoS) attack. This vulnerability arises from the package's failure to properly sanitize the value option passed to the Buffer constructor. As a result, attackers can exploit this flaw by passing large values, leading to the exhaustion of system resources.

Vulnerability Detail

The vulnerability in memjs (CVE-2018-3767) allows attackers to launch a Denial of Service attack on systems using the package. By passing large values to the value option, the package fails to handle them properly, causing the system to exhaust its resources. This can result in the unavailability of the affected system, impacting its performance and potentially disrupting the services it provides. The vulnerability has a moderate severity rating and is classified under CWE-400 (Uncontrolled Resource Consumption).

How To Fix

No fixed version is published for this vulnerability.

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

Conclusion

The memjs package prior to version 1.2.2 is vulnerable to a Denial of Service attack due to improper handling of the value option. To mitigate this risk, it is crucial to upgrade to the latest version of the package. By doing so, developers can ensure the proper sanitization of the value option and prevent the exhaustion of system resources. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for memjs →

Share this vulnerability

FAQ

The vulnerability allows attackers to launch a Denial of Service attack, potentially causing the affected system to become unavailable and impacting its performance.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply upload your package-lock.json file and the tool will analyze it for any open-source vulnerabilities, including CVE-2018-3767.

No, there are no known workarounds for this vulnerability. It is recommended to upgrade to the latest version of the memjs package to fix the issue.

There is no evidence of this vulnerability being actively exploited in the wild. However, it is still important to apply the recommended fix to ensure the security and stability of your application.

This vulnerability was discovered and reported by the GitHub Security Lab.

How To Fix

No fixed version is published for this vulnerability.

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