| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| In Splunk AI Assistant versions below 2.0.0, a user who does not hold the "admin" or "power" Splunk roles could turn on the AI chat training-data consent setting through the Representational State Transfer (REST) API.
The missing authorization is possible because the affected configuration endpoint does not enforce authorization checks. |
| In Splunk AI Assistant versions below 2.0.0, a user who does not hold the "admin" or "power" Splunk roles could obtain limited information about indexes and data sources outside their authorized scope through the assistant.
The vulnerability is possible because Splunk AI Assistant does not fully apply authorization controls to all information that it retrieves. |
| In Splunk AI Assistant versions below 2.0.0 a user who does not hold the "admin" or "power" Splunk roles could access data associated with another tenant and cause actions to be attributed to that tenant through the Representational State Transfer (REST) API.
The vulnerability is possible because Splunk AI Assistant accepted a client-controlled tenant identifier when selecting the authorization context for a request. |
| In Splunk AI Assistant versions below 2.0.0, a user who does not hold the "admin" or "power" Splunk roles could submit client-controlled feature settings through the Representational State Transfer (REST) API. This could modify limited response metadata outside the expected server-side configuration.
The vulnerability is possible because the REST API processes client-supplied feature settings without enforcing the expected server-side configuration boundary. |
| aMQTT is an open source MQTT broker and client. From 0.11.0 until 0.11.4, add_subscription() in amqtt/broker.py accepts malformed single-level + wildcard placement because it checks substrings instead of validating each slash-delimited level. The _matches() function converts each + into a greedy regular-expression fragment and evaluates it with re.fullmatch(), allowing a filter containing many adjacent + characters to trigger catastrophic backtracking when compared with a topic that partially matches but ultimately fails. Because matching runs synchronously in _run_broadcast(), one subscription followed by a publish can block the broker event loop, stopping message delivery and new connection processing until restart. Anonymous clients can trigger the issue with the default configuration. Any authenticated client permitted to create arbitrary subscriptions and publish messages may still exploit it when authentication is enabled. This issue is fixed in version 0.11.4. |
| Go-Guerrilla SMTP Daemon is a lightweight SMTP server written in Go. In 1.6.7 and earlier, according to the repository advisory's structured affected range, server.go defines the seven-byte cmdXCLIENT token, but the XCLIENT handler slices input[8:] after matching only that seven-byte verb, so a bare command causes an out-of-bounds panic in handleClient and terminates the daemon because that connection goroutine does not recover the panic. The issue is reachable by an unauthenticated client when the non-default xclient_on setting is enabled; no HELO command is required. The repository fix is present in version 1.6.7-1. |
| ALTCHA is a Go library for creating and verifying ALTCHA challenges. Prior to 2.1.0, parseServerSignature can leave ServerSignatureVerificationData.Extra uninitialized when url.ParseQuery returns partial values and an error for a malformed percent escape in VerificationData. A later write of an unknown parsed key to the nil map panics before VerifyServerSignature or VerifyServerSignatureSafe completes signature verification, so an unauthenticated client can abort a request. Standard net/http recovers the request goroutine, while application goroutines or frameworks without recovery can crash the process. This issue is fixed in version 2.1.0. |
| BeamNG.drive before 0.40.6 contains an out-of-bounds write vulnerability because JIT-compiled LuaJIT traces omit FFI array bounds checks, letting untrusted Lua escape the sandbox. Attackers supplying a malicious mod can JIT-compile an FFI store loop, write out of range using a tostring() address leak, re-enable ffi.load, and run commands as the game user. |
| PowerLink developed by Neotroni Lighting has a SQL Injection vulnerability, allowing unauthenticated remote attackers to inject arbitrary SQL commands to read database contents. |
| Insertion of Sensitive Information Into Sent Data vulnerability in WP Swings PDF Generator for WordPress pdf-generator-for-wp allows Retrieve Embedded Sensitive Data.This issue affects PDF Generator for WordPress: from n/a through 1.6.5. |
| Insertion of Sensitive Information Into Sent Data vulnerability in WPTasty Tasty Recipes Lite tasty-recipes-lite allows Retrieve Embedded Sensitive Data.This issue affects Tasty Recipes Lite: from n/a through 1.2.11. |
| Authentication Bypass Using an Alternate Path or Channel vulnerability in miniOrange miniorange otp verification miniorange-otp-verification allows Authentication Abuse.This issue affects miniorange otp verification: from n/a through 5.6.1. |
| ImageMagick before 7.1.2-35 contains a heap buffer over-read vulnerability that allows attackers to read beyond allocated heap memory by triggering the -copy operation. Attackers can supply crafted images or arguments processed with -copy to crash the application or disclose adjacent heap memory contents. |
| ImageMagick before 7.1.2-35 contains a policy bypass vulnerability that allows attackers to read from disallowed paths due to a missing policy check when decoding MPC files. Attackers can supply crafted MPC files that reference restricted locations to access files the configured security policy should block. |
| ImageMagick before 7.1.2-35 contains a policy bypass vulnerability in the ASE decoder caused by a missing security policy check. Attackers can supply crafted ASE files that evade configured resource policies to cause excessive memory usage and denial of service. |
| THC-Hydra through 9.7 contains a stack buffer overflow vulnerability in analyze_server_response() of hydra-http-form.c that allows malicious HTTP servers to corrupt memory via crafted Set-Cookie headers. Attackers can send a Set-Cookie header with an extra leading space followed by a repeated cookie name, causing a negative strncpy length that overflows tmpcookie and crashes Hydra. |
| When extra data is allowed (extra=Extra.allow), providing a __pydantic_initialised__ key when validating a Pydantic V1 dataclass makes it considered as already validated, resulting in field values not being validated. The __init__() method of Pydantic V1 dataclasses stores all the provided keyword arguments in the instance __dict__ before validation, so a __pydantic_initialised__ keyword argument overrides the internal flag used to skip validation of already validated instances. As a result, data returned by validation doesn't match the declared type. Affected are applications validating untrusted data into Pydantic V1 dataclasses allowing extra data. The issue was fixed in Pydantic 1.10.27. Users relying on the pydantic.v1 namespace in Pydantic V2 should upgrade to 2.14.2 or later. |
| Frappe is a full-stack web application framework. Prior to 15.108.0 and 16.18.3, the add_comment handler in frappe/templates/includes/comments/comments.py trusts the client-provided comment_by and comment_email fields. A caller can submit chosen identity metadata that is stored with a comment, causing the comment to appear to originate from another name or email address. This issue is fixed in versions 15.108.0 and 16.18.3. |
| Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in InstaWP InstaWP Connect instawp-connect allows Blind SQL Injection.This issue affects InstaWP Connect: from n/a through 0.1.4.4. |
| The Photo Gallery, Sliders, Proofing and Themes – NextGEN Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 4.5.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the plugin's "What must the lightbox be applied to?" setting (thumbEffectContext) to be configured as "Try to apply to all images" or "Try to apply to all images that link to image files," which is not the shipping default, and also requires the attacker's comment to reach a publicly rendered state. |