Sensitive Data Exposure in put

put Updated 02 Oct 2025

Summary

03/09/2020

Disclosed on

LOW

Severity

No i

Fix available

Low

Severity

Not published

CVSS Score

GHSA-v6gv-fg46-h89j: Sensitive Data Exposure in put. Affected versions are not published. 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 Browse

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.

Background

The put package is an npm package used for writing data to a file. It provides a simple and convenient way to create or append content to a file in Node.js. However, all versions of put up to version 6.x are vulnerable to Uninitialized Memory Exposure. This vulnerability occurs due to incorrect calculation of the allocated buffer size and failure to trim the bytes written. As a result, uninitialized memory containing sensitive data may be accessible to attackers.

Vulnerability Detail

The Uninitialized Memory Exposure vulnerability in put allows attackers to access uninitialized memory that may contain sensitive data. This can lead to the exposure of sensitive information, such as passwords, API keys, or other confidential data. The vulnerability affects versions of Node.js up to 6.x. It is important to note that this vulnerability has a low severity level.

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 →

Workaround

There is no specific workaround mentioned for this vulnerability.

Conclusion

In conclusion, the put package in versions up to 6.x is vulnerable to Uninitialized Memory Exposure. This vulnerability can lead to the exposure of sensitive data. It is recommended to upgrade your Node.js version or consider using an alternative package. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for put →