Authlib versions prior to 1.9.0 contain a vulnerability in the OpenID Connect implicit grant implementation where the authorization request's raw scope parameter is checked instead of the filtered allowed scope. This allows a registered OAuth client, which is not permitted the 'openid' scope but allowed other scopes like 'profile', to obtain a signed ID token if the user consents. The ID token includes identity claims such as 'sub' and 'name', effectively bypassing intended scope restrictions. The issue is fixed in version 1.9.0.
Authlib versions from 1.3.1 up to but not including 1.9.0 contain a vulnerability in the handling of HMAC keys in the jose module. The check that prevents asymmetric public keys from being used as HMAC secrets only inspects the start of the key bytes, but the asymmetric key loader skips leading bytes before the PEM header. This discrepancy allows an attacker with only the issuer's public key to craft a valid HS256 token with arbitrary claims that will be accepted as authentic. The issue is an incomplete fix of a previous vulnerability (CVE-2024-37568) and affects the documented usage of the jwt.decode method. A fix is available in version 1.9.0.
PhpSpreadsheet versions from 5.5.0 up to and including 5.9.0 contain a server-side request forgery (SSRF) vulnerability in the Worksheet\Drawing::setPath() method. The vulnerability arises because the external image URL whitelist check is applied only once on the initial URL, and HTTP redirects are followed without re-validation, allowing an attacker to redirect requests to internal or otherwise restricted endpoints. This results in a blind SSRF where the server issues internal GET requests without exfiltrating response content. A fix is available in version 5.10.0.
PhpSpreadsheet's ODS reader has an unbounded number-rows-repeated attribute handling flaw that can cause memory exhaustion. When processing an OpenDocument Spreadsheet (.ods) file, the reader expands the number-rows-repeated attribute without an upper bound, potentially materializing millions of cells from a small file. This leads to PHP fatal out-of-memory errors. All maintained versions up to 5.9.0 are affected. The vulnerability is fixed in versions 5.10.0, 3.10.8, 2.4.8, 2.1.19, and 1.30.7.
PhpSpreadsheet versions prior to 5.10.0, 3.10.8, 2.4.8, 2.1.19, and 1.30.7 contain a vulnerability in the XmlScanner::scan() method. The scanner's regex pattern only accounts for NULL byte interleaving when detecting <!DOCTYPE declarations, but ISO-2022 escape sequences can bypass this detection. This allows malicious XLSX files with crafted XML to include DOCTYPE declarations that enable XML External Entity (XXE) attacks and Denial of Service (DoS) via quadratic entity expansion. The issue affects all PHP versions for DoS and PHP versions below 8.0 or when LIBXML_NOENT is used for XXE/SSRF. A fix is available in the stated versions.
PhpSpreadsheet's XmlScanner performs two scans on XML content, each followed by an entity decoding callback that runs after pattern checks. This allows a double-encoded entity sequence to bypass detection of dangerous <!DOCTYPE declarations, enabling XML External Entity (XXE) injection and Denial of Service (DoS) via entity expansion. The vulnerability affects PhpSpreadsheet versions >=3.3.0 <3.10.8 and >=4.0.0 <5.10.0. It is exploitable for DoS on all PHP versions and for XXE/SSRF on PHP versions below 8.0 or when LIBXML_NOENT is used. Fixed in versions 3.10.8 and 5.10.0.
A vulnerability in github.com/klauspost/compress/zstd versions prior to 1.20.2 causes a panic due to an out-of-range slice index when decompressing crafted two-block zstd frames. The flaw arises from improper handling of Huffman-weight tables in the FSE decoder, leading to reuse of stale state and an invalid decode table. This can crash any program decompressing untrusted zstd input. The issue is fixed in version 1.20.2.
Authlib versions from 0.13 up to 1.7.2 contain a vulnerability in the is_secure_transport() function, which incorrectly treats certain HTTP URLs with userinfo components as secure loopback addresses. This allows an attacker to bypass the TLS enforcement by crafting URLs like http://localhost:80@evil.example/cb, where the actual host is external but the function returns true due to a prefix string match. This flaw affects OAuth 2.0 / OIDC endpoint and redirect URI validation, potentially allowing cleartext HTTP URLs to be accepted where TLS is required. The issue is fixed in Authlib 1.8.0.
A vulnerability in dnspython's dns.name.from_wire_parser() function allows a maliciously crafted DNS message to cause excessive CPU usage during DNS name decompression. This can degrade application performance or lead to denial of service (DoS) when processing untrusted DNS wire format messages. The issue is fixed in dnspython version 2.9.0. No known workarounds exist.
A regular expression denial of service (ReDoS) vulnerability exists in Datadog's dd-trace-py library affecting the URL query string obfuscation pattern used in HTTP tracing integrations. The vulnerable regex can cause excessive CPU consumption and stall request processing when handling certain attacker-controlled inputs, leading to denial of service. This issue affects ddtrace versions from 1.5.0 up to but not including 3.19.9, and from 4.0.0 up to but not including 4.15.6. A fix is available in versions 3.19.9 and 4.15.6. Workarounds involve setting environment variables to use a fixed regex pattern. The vulnerability is enabled by default in affected HTTP integrations that include query strings in URL span tags.
A vulnerability in dd-trace-py's IAST instrumentation can cause a denial of service by terminating the Python application process when processing certain attacker-controlled inputs. This issue affects only applications with IAST enabled, which is disabled by default. The flaw arises from improper handling of internal errors in string-processing instrumentation. Exploitation requires the vulnerable dd-trace-py version with IAST enabled and exposure of the affected operation to attacker input. A fix is available in version 4.15.5.
A vulnerability in the MongoDB Python driver (PyMongo) affects the C extension's BSON decoder when processing malformed Regex elements. This flaw allows an out-of-bounds read past the end of the caller's buffer, potentially causing a process crash via an uncatchable SIGSEGV signal. The issue impacts applications decoding untrusted BSON from mmap or array buffers, which lack NUL termination. The vulnerability affects all PyMongo releases from 3.9.0 up to but not including 4.18.3 when the C extension is loaded. The issue is fixed in version 4.18.3, where malformed Regex elements raise an InvalidBSON exception on all buffer types.
vLLM versions from 0.7.3 up to but not including 0.31.0 have a vulnerability where an attacker can control the mm_processor_kwargs.code_revision parameter in multimodal requests. When the operator enables trust_remote_code and serves a model whose Hugging Face processor uses dynamic auto_map code, this allows the attacker to execute arbitrary Python code by importing a malicious processor module revision. The vulnerability is exploitable via unauthenticated /tokenize endpoints unless protected externally. A fix is available in vLLM version 0.31.0.
The strands-agents FileSessionManager stores session data in a world-writable directory (/tmp/strands/sessions/) using predictable file paths and writes that follow symbolic links. This allows a local attacker to create symlinks to arbitrary files, causing the application to overwrite those files with attacker-controlled session data. This can lead to local privilege escalation by overwriting shell configuration files, SSH keys, cron jobs, or systemd user services. Additionally, the lack of integrity verification on session files enables persistent prompt injection attacks by tampering with session data.
The strands-agents package has a local confidentiality vulnerability in its default FileSessionManager storage. By default, session data is stored under /tmp/strands/sessions with directory and file permissions that allow other local users on shared systems to read sensitive session data. This can expose prompts, model outputs, tool inputs/outputs, intermediate states, and secrets stored in session files. The issue arises because the storage directories and files are created with permissions relying on the process umask, commonly 022, resulting in directories with 0755 and files with 0644 permissions. A fix is available in version 1.48.0 that addresses these permission issues.
A heap buffer overflow vulnerability exists in the Snappy.uncompress*Array typed-array methods of snappy-java before version 1.1.10.9. The issue arises because the methods size the result array by dividing the declared uncompressed byte length by the element size, but native code writes the full byte length, potentially writing up to 7 bytes past the end of the Java array if the length is not a multiple of the element size. This heap corruption can lead to application instability or crashes. The vulnerability is fixed in version 1.1.10.9, where the methods now reject uncompressed lengths that are not multiples of the element size by throwing a SnappyIOException. Users can mitigate by verifying the uncompressed length is a multiple of the element size before calling these methods.
A vulnerability in snappy-java prior to version 1.1.10.9 allows JVM crashes due to unchecked array range parameters in Snappy.arrayCopy and related stream read/write methods. The flaw arises from native memcpy calls without validating offsets and lengths, leading to out-of-bounds memory access and JVM crashes. This issue has been fixed in version 1.1.10.9 by adding proper range checks.
Several decompression functions in snappy-java versions prior to 1.1.10.9 allocate memory based on the uncompressed length declared in the compressed data without proper validation. This can lead to excessive memory allocation up to 2 GB or trigger exceptions, causing denial of service. The issue affects multiple entry points including Snappy.uncompress methods and input streams. The vulnerability is fixed in version 1.1.10.9 by validating and limiting the declared uncompressed length relative to the compressed input size.
A vulnerability in Grav versions from 1.7.53.3 up to but not including 1.7.53.6 allows unauthorized users to bypass authorization checks in the Debugger::isDebuggerRequestAuthorized() function. This flaw enables unauthenticated visitors to access /__clockwork/ profiler data by exploiting a fallback to loopback REMOTE_ADDR. When Grav is behind a same-host reverse proxy, remote requests can be treated as loopback, allowing attackers to read sensitive stored records such as administrator plaintext passwords and configuration credentials.
A race condition vulnerability exists in a2aproject a2a-java up to version 1.2.0.Final in the TaskManager.saveTaskEvent function. This vulnerability can be exploited remotely and may lead to integrity and availability impacts. Upgrading to version 1.3.0.Final resolves the issue.