CVE-2020-25340: Memory Leak Vulnerability in nfstream

nfstream Updated 02 Oct 2025

Summary

16/02/2021
Yes i
Moderate
5.5

CVE-2020-25340: An issue was discovered in NFStream 5.2.0. Affects nfstream versions < 6.0.0. Fixed in 6.0.0. 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

nfstream is a Python library that provides network traffic analysis capabilities. It allows users to capture, analyze, and visualize network flows. The library is commonly used for network monitoring, security analysis, and performance optimization. However, version 5.2.0 of nfstream is vulnerable to a memory leak issue that can lead to a local denial of service (DoS) attack.

Vulnerability Detail

The vulnerability in nfstream version 5.2.0 arises from the improper handling of allocated modules. When the nfstream object is created but not used before being destroyed, certain modules are not correctly freed, resulting in a memory leak. This memory leak can be exploited by an attacker to exhaust system resources, leading to a DoS condition. The impact of this vulnerability is limited to local attacks, as it requires direct access to the affected system.

How To Fix

Minimum fixed version

6.0.0

This is the first release that contains the fix.

pip install --upgrade "nfstream==6.0.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround provided for this vulnerability. It is advised to update to the latest version of nfstream as soon as possible.

Conclusion

The memory leak vulnerability in nfstream version 5.2.0 can be mitigated by upgrading to version 6.0.0 or later. It is crucial to promptly update the library to ensure system security and prevent potential denial of service attacks. For further assistance or support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for nfstream →

Share this vulnerability

FAQ

nfstream is a Python library used for network traffic analysis, allowing users to capture, analyze, and visualize network flows.

The vulnerability can be exploited to cause a local denial of service (DoS) attack by exhausting system resources.

No, this vulnerability can only be exploited locally as it requires direct access to the affected system.

To fix this vulnerability, update nfstream to version 6.0.0 or later.

No specific workarounds have been provided. It is recommended to update to the latest version.

How To Fix

Minimum fixed version

6.0.0

This is the first release that contains the fix.

pip install --upgrade "nfstream==6.0.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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