
Explore packages and vulnerabilities by …
Operating system
Infrastructure as Code
Vulnerabilities from the last week
Malicious Package
testpackage83 is a malicious package. This package contains malicious code, and its content was removed from the official package manager. While this package might be attempting to impersonate a valid organization, there is no connection between that organization and this package authorship.
Inefficient Algorithmic Complexity
nltk is a Natural Language Toolkit (NLTK) is a Python package for natural language processing.
Affected versions of this package are vulnerable to Inefficient Algorithmic Complexity via SteppingRecursiveDescentParser.parse() in nltk/parse/recursivedescent.py, which performs an unbounded top-down search over ambiguous or self-embedding context-free grammars with no wall-clock or step limit. The base class RecursiveDescentParser arms a max_time wall-clock deadline inside _parse, but the stepping subclass overrides both parse() and _parse(), drives its own while self.step() is not None loop that never enters the guarded base _parse, and its constructor omits the max_time parameter entirely, so the deadline cannot be enabled on this path. An attacker who can influence the grammar and supply a short token sequence to a caller that invokes parse() can force the call to pin a CPU core indefinitely, exhausting a bounded worker pool.
Note: This is only exploitable when the target uses SteppingRecursiveDescentParser on attacker-influenced grammar or input; the stepping parser is primarily a debugging and interactive-stepping component, so real-world exposure is narrower than for the base parser.
Insertion of Sensitive Information into Log File
org.webjars.npm:undici is an An HTTP/1.1 client, written from scratch for Node.js
Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File via the cleanRequestHeaders function in lib/handler/redirect-handler.js, when request headers are supplied as an array of [name, value] tuples (e.g. via Object.entries(headers)). The redirect interceptor is responsible for stripping sensitive headers such as Authorization, Cookie, Proxy-Authorization, and Host on cross-origin redirects, but it misreads tuple-format headers as a flat alternating [name, value, name, value, ...] list, causing header names to never match the strip list and leaving sensitive headers intact. When a header-normalizing interceptor such as cache() or deduplicate() is composed outside redirect(), it serializes the retained headers onto the cross-origin request, disclosing origin-bound credentials to the redirect destination. This is a representation-dependent bypass of the cross-origin header stripping introduced to address CVE-2024-30260.
Note: This is only exploitable when headers are supplied as an array of [name, value] tuples and a header-normalizing interceptor (cache() or deduplicate()) is composed outside the redirect() interceptor.
Recent vulnerabilities disclosed by Snyk
- M
Cross-site Scripting (XSS) in nice-select2 (npm)- C
Malicious Package in cacheutilskit (npm)- C
Malicious Package in byteutilsbox (npm)- C
Malicious Package in streamlyx (npm)- H
Directory Traversal in zip-lib (npm)
Snyk security
researchers
have disclosed
3506
vulnerabilities
About Snyk dependencies vulnerability database
Snyk is a developer security platform. Integrating directly into development tools, workflows, and automation pipelines, Snyk makes it easy for teams to find, prioritize, and fix security vulnerabilities in code, dependencies, containers, and infrastructure as code. Supported by industry-leading application and security intelligence, Snyk puts security expertise in any developer's toolkit.




