CVE Vulnerability Catalog

MailKit versions prior to 4.16.0 contain a STARTTLS Response Injection vulnerability. A man-in-the-middle attacker can inject arbitrary protocol responses across the plaintext-to-TLS trust boundary, enabling SASL authentication mechanism downgrade (e.g., forcing PLAIN instead of SCRAM-SHA-256). The internal read buffer in SmtpStream, ImapStream, and Pop3Stream is not flushed when the underlying stream is replaced with SslStream during STARTTLS upgrade.

AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. Prior to version 1.12.1, AnythingLLM's in-chat markdown renderer has an unsafe custom rule for images that interpolates the markdown image's alt text into an HTML alt="..." attribute without any HTML encoding. Every call-site in the app wraps renderMarkdown(...) with DOMPurify.sanitize(...) as defense-in-depth — except the Chartable component, which renders chart captions with no sanitization. The chart caption is the natural-language text the LLM emits around a create-chart tool call, so any attacker who can influence the LLM's output — most cheaply via indirect prompt injection in a shared workspace document, or directly if they can create a chart record in a multi-user workspace — can trigger stored DOM-level XSS in every other user's browser when they open that conversation. AnythingLLM chat history is loaded server-side via GET /api/workspace/:slug/chats and rendered directly into the chat UI. Version 1.12.1 contains a patch for this issue.

The go-ntlmssp package before version 0.1.1 contains a vulnerability that causes a slice out of bounds panic when processing a malicious NTLM challenge message. This can crash any Go process using `ntlmssp.Negotiator` as an HTTP transport.

Kirby prior to versions 4.9.0 and 5.4.0 checked the pages.create and pages.changeStatus permissions independently, so changeStatus did not apply on page creation. An authenticated attacker with pages.create could override the isDraft flag via the REST API and immediately create published pages, bypassing the editorial workflow.

Prior to version 4.4.1, any authenticated Xibo user can manually construct a URL to preview campaigns/regions and export saved reports belonging to other users. Exploitation is possible on behalf of an authorized user with privileges to Layout Management, Campaign Management, or Saved Reports pages. Users should upgrade to version 4.4.1 which fixes this issue.

Xibo prior to version 4.4.1 contains an authenticated SSRF vulnerability that allows users with DataSet permissions to make arbitrary HTTP requests from the CMS server to internal or external resources. This can be exploited to scan infrastructure, access cloud metadata endpoints (e.g., AWS IMDS), or exfiltrate data.

Xibo (an open source digital signage platform with a web CMS and Windows player) prior to 4.4.1 contains a stored XSS vulnerability. An authenticated user with notification creation permissions can inject arbitrary JavaScript into the notification body. When the notification is set as an "interrupt," the payload executes automatically in the browser of any targeted user upon login, requiring zero user interaction. This requires Notification Centre access and the "Add Notification" button, which are not granted to non-admins by default. Fixed in 4.4.1.

The SenseLive X3050 web management interface relies on unencrypted HTTP for all administrative communication. Authentication attempts and configuration data are transmitted in cleartext, allowing an attacker on the same network segment to intercept sensitive operational information.

In versions <8.4.0, <8.3.2, <8.2.2, <8.1.3, <8.0.4, <7.13.6, <7.12.7, <7.11.7, and <7.10.10, the /api/apps/logs and /api/apps/:id/logs endpoints have a typo in the required permission check, allowing authenticated users without proper permissions to read apps-engine logs.

melange versions 0.32.0 through before 0.43.4 construct output file paths in --persist-lint-results by joining --out-dir with arch and pkgname from the APK's .PKGINFO without validating path separators or '..' sequences. An attacker supplying an APK to a melange lint/build pipeline could cause a JSON lint report to be written to an arbitrary reachable path. There is no direct code execution, but other JSON artifacts can be clobbered. The issue is fixed in 0.43.4.

melange (a tool for building apk packages using declarative pipelines) from version 0.32.0 to before 0.43.4 allows an attacker who can influence a melange configuration file to set pipeline[].uses to a value containing ../ sequences or an absolute path. The (*Compiled).compilePipeline function in pkg/build/compile.go passed uses directly to filepath.Join(pipelineDir, uses + ".yaml") without validation, so the resolved path could escape --pipeline-dir and read any YAML-parseable file visible to the melange process. Because the loaded file is interpreted as a melange pipeline and its runs: block is executed via /bin/sh -c in the build sandbox, this allowed shell commands from an out-of-tree file to run during the build, bypassing review. Fixed in melange v0.43.4 (commit 5829ca4).

The SenseLive X3050 web management interface does not properly enforce session lifetime, allowing authenticated sessions to remain active for extended periods without re-authentication. An attacker with access to a previously authenticated session can continue using administrative functions.

A vulnerability in the browser-based remote management interface may allow an administrator to access sensitive information on the device via crafted requests. It affects certain production printers and office/small office multifunction printers.

A type confusion flaw was found in libxml2 when processing a specially crafted XML Schema Definition (XSD) validated document that includes an internal entity reference. An attacker can exploit this by providing a malicious document, causing the application to crash.

radare2 prior to 6.1.4 contains a path traversal vulnerability in its project notes handling that allows attackers to read or write files outside the configured project directory by importing a malicious .zrp archive containing a symlinked notes.txt file. Attackers can bypass directory confinement checks, allowing note operations to follow the symlink and access arbitrary files outside the dir.projects root directory.

SWUpdate contains an integer underflow vulnerability in the multipart upload parser in mongoose_multipart.c that allows unauthenticated attackers to cause a denial of service by sending a crafted HTTP POST request to /upload with a malformed multipart boundary and controlled TCP stream timing. Attackers can trigger an integer underflow in the mg_http_multipart_continue_wait_for_chunk() function when the buffer length falls within a specific range, causing an out-of-bounds heap read past the allocated receive buffer to a local IPC socket.

Moduł @node-oauth/oauth2-server w Node.js ma lukę, która pozwala na akceptację nieprawidłowych wartości code_verifier zgodnych z RFC7636, w tym jednoczłonowych ciągów, w przepływach S256 PKCE. To umożliwia atakującym przeprowadzanie ataków brute-force na code_verifier po przechwyceniu kodu autoryzacyjnego.

In the AWS X-Ray Remote Sampler package (OpenTelemetry.Sampler.AWS) prior to 0.1.0-alpha.8, unbounded HTTP response bodies are read from a configured AWS X-Ray remote sampling endpoint into memory. AWSXRaySamplerClient.DoRequestAsync calls HttpClient.SendAsync followed by ReadAsStringAsync(), materializing the entire response body into a single in-memory string with no size limit. An attacker controlling the endpoint or intercepting traffic (MitM) can return an arbitrarily large response body, causing memory exhaustion.

OpenTelemetry.Exporter.Jaeger in version 1.6.0-rc.1 and earlier may cause sustained memory pressure when the internal pooled-list sizing grows based on a large observed span/tag set and that enlarged size is reused. Under high-cardinality or attacker-influenced telemetry input, this can increase memory consumption and potentially cause denial of service. There is no plan to fix this issue as the exporter was deprecated in 2023.

OpenTelemetry dotnet is a .NET telemetry framework. In OpenTelemetry.Api 0.5.0-beta.2 to 1.15.2 and OpenTelemetry.Extensions.Propagators 1.3.1 to 1.15.2, the baggage, B3 and Jaeger processing implementation can allocate excessive memory when parsing, potentially causing a denial of service (DoS) in the consuming application. The vulnerability is fixed in 1.15.3.