deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-jjph-296x-mrcr
Package: transformers (PIP)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-1333: Inefficient Regular Expression Complexity
Vulnerable versions: < 4.51.0
Patched in: 4.51.0

Summary: Transformers vulnerable to ReDoS attack through its get_imports() function

Details:
A Regular Expression Denial of Service (ReDoS) vulnerability was discovered in the Hugging Face Transformers library, specifically in the `get_imports()` function within `dynamic_module_utils.py`. This vulnerability affects versions 4.49.0 and is fixed in version 4.51.0. The issue arises from a regular expression pattern `\s*try\s*:.*?except.*?:` used to filter out try/except blocks from Python code, which can be exploited to cause excessive CPU consumption through crafted input strings due to catastrophic backtracking. This vulnerability can lead to remote code loading disruption, resource exhaustion in model serving, supply chain attack vectors, and development pipeline disruption.
GitHub Security Advisory: GHSA-q2wp-rjmx-x6x9
Package: transformers (PIP)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-1333: Inefficient Regular Expression Complexity
Vulnerable versions: < 4.51.0
Patched in: 4.51.0

Summary: Transformers's ReDoS vulnerability in get_configuration_file can lead to catastrophic backtracking

Details:
A Regular Expression Denial of Service (ReDoS) vulnerability was discovered in the Hugging Face Transformers library, specifically in the `get_configuration_file()` function within the `transformers.configuration_utils` module. The affected version is 4.49.0, and the issue is resolved in version 4.51.0. The vulnerability arises from the use of a regular expression pattern `config\.(.*)\.json` that can be exploited to cause excessive CPU consumption through crafted input strings, leading to catastrophic backtracking. This can result in model serving disruption, resource exhaustion, and increased latency in applications using the library.
GitHub Security Advisory: GHSA-p7j4-jwjf-5x9w
Package: llama-index-readers-papers (PIP)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-440: Expected Behavior Violation
Vulnerable versions: < 0.3.1
Patched in: 0.3.1

Summary: LlamaIndex vulnerability in ArxivReader class can cause MD5 hash collisions

Details:
A vulnerability in the ArxivReader class of the run-llama/llama_index repository allows for MD5 hash collisions when generating filenames for downloaded papers. This can lead to data loss as papers with identical titles but different contents may overwrite each other, preventing some papers from being processed for AI model training. The issue is resolved in llama-index-readers-papers version 0.3.1 (in llama-index 0.12.28).
GitHub Security Advisory: GHSA-w42r-mrx7-c633
Package: llama-index-readers-papers (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-776: Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')
Vulnerable versions: < 0.3.2
Patched in: 0.3.2

Summary: LlamaIndex has an XML Entity Expansion vulnerability in its sitemap parser

Details:
An XML Entity Expansion vulnerability, also known as a 'billion laughs' attack, exists in the sitemap parser of the run-llama/llama_index repository, specifically affecting the Papers Loaders package before version 0.3.2 (in llama-index v0.10.0 and above through v0.12.29). This vulnerability allows an attacker to supply a malicious Sitemap XML, leading to a Denial of Service (DoS) by exhausting system memory and potentially causing a system crash. The issue is resolved in version 0.3.2 (in llama-index 0.12.29).
GitHub Security Advisory: GHSA-489j-g2vx-39wf
Package: transformers (PIP)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-1333: Inefficient Regular Expression Complexity
Vulnerable versions: >= 4.49.0, < 4.51.0
Patched in: 4.51.0

Summary: Transformers vulnerable to ReDoS attack through its SETTING_RE variable

Details:
A Regular Expression Denial of Service (ReDoS) vulnerability was discovered in the huggingface/transformers repository, specifically in version 4.49.0. The vulnerability is due to inefficient regular expression complexity in the `SETTING_RE` variable within the `transformers/commands/chat.py` file. The regex contains repetition groups and non-optimized quantifiers, leading to exponential backtracking when processing 'almost matching' payloads. This can degrade application performance and potentially result in a denial-of-service (DoS) when handling specially crafted input strings. The issue is fixed in version 4.51.0.
GitHub Security Advisory: GHSA-j47q-rc62-w448
Package: fastapi-guard (PIP)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-1333: Inefficient Regular Expression Complexity
Vulnerable versions: <= 3.0.0
Patched in: 3.0.1

Summary: fastapi-guard is vulnerable to ReDoS through inefficient regex

Details:
### Summary

fastapi-guard detects penetration attempts by using regex patterns to scan incoming requests. However, some of the regex patterns used in detection are extremely inefficient and can cause polynomial complexity backtracks when handling specially crafted inputs.

It is not as severe as _exponential_ complexity ReDoS, but still downgrades performance and allows DoS exploits. An attacker can trigger high cpu usage and make a service unresponsive for hours by sending a single request in size of KBs.

### PoC

e.g. https://github.com/rennf93/fastapi-guard/blob/1e6c2873bfc7866adcbe5fc4da72f2d79ea552e7/guard/handlers/suspatterns_handler.py#L31C79-L32C7

```python
payload = lambda n: '<'*n+ ' '*n+ 'style=' + '"'*n + ' '*n+ 'url('*n # complexity: O(n^5)

print(requests.post("http://172.24.1.3:8000/", data=payload(50)).elapsed) # 0:00:03.771120
print(requests.post("http://172.24.1.3:8000/", data=payload(100)).elapsed) # 0:01:17.952637
print(requests.post("http://172.24.1.3:8000/", data=payload(200)).elapsed) # timeout (>15min)
```

Single-threaded uvicorn workers can not handle any other concurrent requests during the elapsed time.

### Impact

Penetration detection is enabled by default. Services that use fastapi-guard middleware without explicitly setting `enable_penetration_detection=False` are vulnerable to DoS.
GitHub Security Advisory: GHSA-fmrf-6jv9-qjc7
Package: llama-index-readers-obsidian (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: < 0.5.1
Patched in: 0.5.1

Summary: LlamaIndex is vulnerable to Path Traversal attack through its ObsidianReader class

Details:
A vulnerability in the `ObsidianReader` class in LlamaIndex Readers Integration: Obsidian before version 0.5.1 from the run-llama/llama_index repository (versions 0.12.23 to 0.12.28) allows for arbitrary file read through symbolic links. The `ObsidianReader` fails to resolve symlinks to their real paths and does not validate whether the resolved paths lie within the intended directory. This flaw enables attackers to place symlinks pointing to files outside the vault directory, which are then processed as valid Markdown files, potentially exposing sensitive information.
GitHub Security Advisory: GHSA-m84c-4c34-28gf
Package: llama-index-core (PIP)
Severity: MODERATE (CVSS 5.0)
CWE: CWE-1112: Incomplete Documentation of Program Execution
Vulnerable versions: >= 0.11.15, <= 0.12.40
Patched in: 0.12.41

Summary: LlamaIndex has Incomplete Documentation of Program Execution related to JsonPickleSerializer component

Details:
Incomplete Documentation of Program Execution exists in the run-llama/llama_index library's JsonPickleSerializer component, affecting versions v0.12.27 through v0.12.40. This vulnerability allows remote code execution due to an insecure fallback to Python's pickle module. JsonPickleSerializer prioritizes deserialization using pickle.loads(), which can execute arbitrary code when processing untrusted data. Attackers can exploit this by crafting malicious payloads to achieve full system compromise. The root cause involves the use of an insecure fallback strategy without sufficient input validation or protective safeguards. Version 0.12.41 renames JsonPickleSerializer to PickleSerializer and adds a warning to the docs to only use PickleSerializer to deserialize safe things.
GitHub Security Advisory: GHSA-p3xv-97g8-4wmj
Package: python-swiftclient (PIP)
Severity: CRITICAL (CVSS 9.1)
CWE: CWE-295: Improper Certificate Validation
Vulnerable versions: >= 1.0, < 2.0
Patched in: 2.0

Summary: Python Swift client is vulnerable to Missing SSL Certificate Check

Details:
The OpenStack Python client library for Swift (python-swiftclient) from 1.0 before 2.0 does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.
GitHub Security Advisory: GHSA-3qhf-m339-9g5v
Package: mcp (PIP)
Severity: HIGH (CVSS 0.0)
CWE: CWE-248: Uncaught Exception
Vulnerable versions: < 1.9.4
Patched in: 1.9.4

Summary: MCP Python SDK vulnerability in the FastMCP Server causes validation error, leading to DoS

Details:
A validation error in the MCP SDK can cause an unhandled exception when processing malformed requests, resulting in service unavailability (500 errors) until manually restarted. Impact may vary depending on the deployment conditions, and presence of infrastructure-level resilience measures.

Thank you to Rich Harang for reporting this issue.
GitHub Security Advisory: GHSA-j975-95f5-7wqh
Package: mcp (PIP)
Severity: HIGH (CVSS 0.0)
CWE: CWE-248: Uncaught Exception
Vulnerable versions: < 1.10.0
Patched in: 1.10.0

Summary: MCP Python SDK has Unhandled Exception in Streamable HTTP Transport, Leading to Denial of Service

Details:
If a client deliberately triggers an exception after establishing a streamable HTTP session, this can lead to an uncaught ClosedResourceError on the server side, causing the server to crash and requiring a restart to restore service. Impact may vary depending on the deployment conditions, and presence of infrastructure-level resilience measures.

Thank you to Rich Harang for reporting this issue.
GitHub Security Advisory: GHSA-5fc3-pqf2-57cx
Package: apache-iotdb (PIP)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Vulnerable versions: >= 2.0.1b0, < 2.0.2
Patched in: 2.0.2

Summary: Apache IoTDB Discloses Sensitive Information via Log Files

Details:
Exposure of Sensitive Information to an Unauthorized Actor, Insertion of Sensitive Information into Log File vulnerability in the OpenIdAuthorizer of Apache IoTDB.

This issue affects Apache IoTDB: from 0.10.0 through 1.3.3, from 2.0.1-beta before 2.0.2.

Users are recommended to upgrade to version 1.3.4 and 2.0.2, which fix the issue.
GitHub Security Advisory: GHSA-5fc3-pqf2-57cx
Package: apache-iotdb (PIP)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Vulnerable versions: >= 0.10.0, < 1.3.4
Patched in: 1.3.4

Summary: Apache IoTDB Discloses Sensitive Information via Log Files

Details:
Exposure of Sensitive Information to an Unauthorized Actor, Insertion of Sensitive Information into Log File vulnerability in the OpenIdAuthorizer of Apache IoTDB.

This issue affects Apache IoTDB: from 0.10.0 through 1.3.3, from 2.0.1-beta before 2.0.2.

Users are recommended to upgrade to version 1.3.4 and 2.0.2, which fix the issue.
GitHub Security Advisory: GHSA-f4rq-f4j9-f6rm
Package: apache-iotdb (PIP)
Severity: CRITICAL (CVSS 9.8)
CWE: CWE-94: Improper Control of Generation of Code ('Code Injection')
Vulnerable versions: >= 1.0.0, < 1.3.4
Patched in: 1.3.4

Summary: Apache IoTDB Vulnerable to Remote Code Execution

Details:
Remote Code Execution with untrusted URI of UDF vulnerability in Apache IoTDB. The attacker who has privilege to create UDF can register malicious function from untrusted URI.

This issue affects Apache IoTDB: from 1.0.0 before 1.3.4.

Users are recommended to upgrade to version 1.3.4, which fixes the issue.
GitHub Security Advisory: GHSA-xg8h-j46f-w952
Package: pillow (PIP)
Severity: HIGH (CVSS 7.1)
CWE: CWE-122: Heap-based Buffer Overflow
Vulnerable versions: >= 11.2.0, < 11.3.0
Patched in: 11.3.0

Summary: Pillow vulnerability can cause write buffer overflow on BCn encoding

Details:
There is a heap buffer overflow when writing a sufficiently large (>64k encoded with default settings) image in the DDS format due to writing into a buffer without checking for available space. 

This only affects users who save untrusted data as a compressed DDS image. 

* Unclear how large the potential write could be. It is likely limited by process segfault, so it's not necessarily deterministic. It may be practically unbounded. 
* Unclear if there's a restriction on the bytes that could be emitted. It's likely that the only restriction is that the bytes would be emitted in chunks of 8 or 16. 

This was introduced in Pillow 11.2.0 when the feature was added.
GitHub Security Advisory: GHSA-48p4-8xcf-vxj5
Package: urllib3 (PIP)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Vulnerable versions: >= 2.2.0, < 2.5.0
Patched in: 2.5.0

Summary: urllib3 does not control redirects in browsers and Node.js

Details:
urllib3 [supports](https://urllib3.readthedocs.io/en/2.4.0/reference/contrib/emscripten.html) being used in a Pyodide runtime utilizing the [JavaScript Fetch API](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API) or falling back on [XMLHttpRequest](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest). This means you can use Python libraries to make HTTP requests from your browser or Node.js. Additionally, urllib3 provides [a mechanism](https://urllib3.readthedocs.io/en/2.4.0/user-guide.html#retrying-requests) to control redirects.

However, the `retries` and `redirect` parameters are ignored with Pyodide; the runtime itself determines redirect behavior.


## Affected usages

Any code which relies on urllib3 to control the number of redirects for an HTTP request in a Pyodide runtime.


## Impact

Redirects are often used to exploit SSRF vulnerabilities. An application attempting to mitigate SSRF or open redirect vulnerabilities by disabling redirects may remain vulnerable if a Pyodide runtime redirect mechanism is unsuitable.


## Remediation

If you use urllib3 in Node.js, upgrade to a patched version of urllib3.

Unfortunately, browsers provide no suitable way which urllib3 can use: `XMLHttpRequest` provides no control over redirects, the Fetch API returns `opaqueredirect` responses lacking data when redirects are controlled manually. Expect default browser behavior for redirects.
GitHub Security Advisory: GHSA-rvqx-wpfh-mfx7
Package: langflow-base (PIP)
Severity: CRITICAL (CVSS 0.0)
CWE: CWE-94: Improper Control of Generation of Code ('Code Injection')
Vulnerable versions: < 0.3.0
Patched in: 0.3.0

Summary: Langflow Unauth RCE

Details:
Langflow versions prior to 1.3.0 are susceptible to code injection in the /api/v1/validate/code endpoint. A remote and unauthenticated attacker can send crafted HTTP requests to execute arbitrary code.
GitHub Security Advisory: GHSA-v9w6-9hq9-33ch
Package: lightrag-hku (PIP)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: < 1.3.8
Patched in: 1.3.8

Summary: HKUDS LightRAG allows Path Traversal via function upload_to_input_dir

Details:
A vulnerability was found in HKUDS LightRAG up to 1.3.8. It has been declared as critical. Affected by this vulnerability is the function upload_to_input_dir of the file lightrag/api/routers/document_routes.py of the component File Upload. The manipulation of the argument file.filename leads to path traversal. It is possible to launch the attack on the local host. The identifier of the patch is 60777d535b719631680bcf5d0969bdef79ca4eaf. It is recommended to apply a patch to fix this issue.
GitHub Security Advisory: GHSA-9r64-3wmc-x8m8
Package: apache-airflow-providers-snowflake (PIP)
Severity: CRITICAL (CVSS 9.8)
CWE: CWE-75: Failure to Sanitize Special Elements into a Different Plane (Special Element Injection)
Vulnerable versions: < 6.4.0
Patched in: 6.4.0

Summary: Apache Airflow Providers Snowflake package allows for Special Element Injection via CopyFromExternalStageToSnowflakeOperator

Details:
Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) vulnerability in Apache Airflow Providers Snowflake.

This issue affects Apache Airflow Providers Snowflake: before 6.4.0.

Sanitation of table and stage parameters were added in CopyFromExternalStageToSnowflakeOperator to prevent SQL injection
Users are recommended to upgrade to version 6.4.0, which fixes the issue.
GitHub Security Advisory: GHSA-m435-9v6r-v5f6
Package: mobsf (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-918: Server-Side Request Forgery (SSRF)
Vulnerable versions: < 3.9.7
Patched in: 3.9.7

Summary: MobSF vulnerability allows SSRF due to the allow_redirects=True parameter

Details:
### Summary
The fix for the "SSRF Vulnerability on assetlinks_check(act_name, well_knowns)" vulnerability could potentially be bypassed.

### Details
Since the requests.get() request in the _check_url method is specified as allow_redirects=True, if "https://mydomain.com/.well-known/assetlinks.json" returns a 302 redirect, subsequent requests will be sent automatically. If the redirect location is "http://192.168.1.102/user/delete/1", a request will be sent here as well.

<img width="610" alt="image" src="https://github.com/MobSF/Mobile-Security-Framework-MobSF/assets/150332295/a8c9630e-3d12-441a-816c-8f5e427a5194">

It will be safer to use allow_redirects=False.

### Impact
The attacker can cause the server to make a connection to internal-only services within the organization's infrastructure.
GitHub Security Advisory: GHSA-8gff-cf92-72pv
Package: pyspur (PIP)
Severity: LOW (CVSS 6.3)
CWE: CWE-791: Incomplete Filtering of Special Elements
Vulnerable versions: <= 0.1.18
Patched in: unpatched

Summary: pyspur Incomplete Filtering of Special Elements allowed by SingleLLMCallNode function

Details:
A vulnerability was found in PySpur-Dev pyspur up to 0.1.18. It has been classified as critical. Affected is the function SingleLLMCallNode of the file backend/pyspur/nodes/llm/single_llm_call.py of the component Jinja2 Template Handler. The manipulation of the argument user_message leads to improper neutralization of special elements used in a template engine. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.
GitHub Security Advisory: GHSA-hwpg-x5hw-vpv9
Package: changedetection.io (PIP)
Severity: HIGH (CVSS 0.0)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: <= 0.50.3
Patched in: 0.50.4

Summary: ChangeDetection.io XSS in watch overview

Details:
### Impact
XSS - Errors in filters from website page change detection watches were not being filtered.

### Patches

0.50.4
GitHub Security Advisory: GHSA-6qhv-4h7r-2g9m
Package: rfc3161-client (PIP)
Severity: CRITICAL (CVSS 0.0)
CWE: CWE-347: Improper Verification of Cryptographic Signature
Vulnerable versions: <= 1.0.2
Patched in: 1.0.3

Summary: rfc3161-client has insufficient verification for timestamp response signatures

Details:
### Impact

`rfc3161-client` 1.0.2 and earlier contain a flaw in their timestamp response signature verification logic. In particular, it performs chain verification against the TSR's embedded certificates up to the trusted root(s), but fails to verify the TSR's own signature against the timestamping leaf certificates. Consequently, vulnerable versions perform insufficient signature validation to properly consider a TSR verified, as the attacker can introduce _any_ TSR signature so long as the embedded leaf chains up to some root TSA.

### Patches

Users should immediately upgrade to `rfc3161-client` 1.0.3 or later.

### Workarounds

There is no workaround possible. Users should immediately upgrade to a fixed version.
GitHub Security Advisory: GHSA-pq67-6m6q-mj2v
Package: urllib3 (PIP)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Vulnerable versions: < 2.5.0
Patched in: 2.5.0

Summary: urllib3 redirects are not disabled when retries are disabled on PoolManager instantiation

Details:
urllib3 handles redirects and retries using the same mechanism, which is controlled by the `Retry` object. The most common way to disable redirects is at the request level, as follows:

```python
resp = urllib3.request("GET", "https://httpbin.org/redirect/1", redirect=False)
print(resp.status)
# 302
```

However, it is also possible to disable redirects, for all requests, by instantiating a `PoolManager` and specifying `retries` in a way that disable redirects:

```python
import urllib3

http = urllib3.PoolManager(retries=0)  # should raise MaxRetryError on redirect
http = urllib3.PoolManager(retries=urllib3.Retry(redirect=0))  # equivalent to the above
http = urllib3.PoolManager(retries=False)  # should return the first response

resp = http.request("GET", "https://httpbin.org/redirect/1")
```

However, the `retries` parameter is currently ignored, which means all the above examples don't disable redirects.

## Affected usages

Passing `retries` on `PoolManager` instantiation to disable redirects or restrict their number.

By default, requests and botocore users are not affected.

## Impact

Redirects are often used to exploit SSRF vulnerabilities. An application attempting to mitigate SSRF or open redirect vulnerabilities by disabling redirects at the PoolManager level will remain vulnerable.

## Remediation

You can remediate this vulnerability with the following steps:

 * Upgrade to a patched version of urllib3. If your organization would benefit from the continued support of urllib3 1.x, please contact [sethmichaellarson@gmail.com](mailto:sethmichaellarson@gmail.com) to discuss sponsorship or contribution opportunities.
 * Disable redirects at the `request()` level instead of the `PoolManager()` level.
GitHub Security Advisory: GHSA-g2xh-c426-v8mf
Package: vyper (PIP)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-670: Always-Incorrect Control Flow Implementation
Vulnerable versions: <= 0.4.2
Patched in: unpatched

Summary: Vyper: reversed order of side effects for some operations

Details:
### Impact

For the following (probably non-exhaustive) list of expressions, the compiler evaluates the arguments from right to left instead of left to right.

```
- unsafe_add
- unsafe_sub
- unsafe_mul
- unsafe_div
- pow_mod256
- |, &, ^ (bitwise operators)
- bitwise_or (deprecated)
- bitwise_and (deprecated)
- bitwise_xor (deprecated)
- raw_call
- <, >, <=, >=, ==, !=
- in, not in (when lhs and rhs are enums)
```

This behaviour becomes a problem when the evaluation of one of the arguments produces side effects that other arguments depend on. The following expressions can produce side-effect:

- state modifying external call 
- state modifying internal call
- `raw_call`
- `pop()` when used on a Dynamic Array stored in the storage
- `create_minimal_proxy_to`
- `create_copy_of`
- `create_from_blueprint`

For example:

```Vyper
f:uint256

@internal
def side_effect() -> uint256:
    self.f = 12
    return 1

@external
def foo() -> uint256:
    return unsafe_add(self.f,self.side_effect()) # returns 13 instead of 1
```

```Vyper
a:DynArray[uint256, 12]
@external
def bar() -> bool:
    self.a = [1,2,3]
    return len(self.a) == self.a.pop() # return false instead of true
```

### Patches
not yet patched, will address in a future release. tracking in https://github.com/vyperlang/vyper/issues/3604.

### Workarounds

When using expressions from the list above, make sure that the arguments of the expression do not produce side effects or, if one does, that no other argument is dependent on those side effects.

### References
_Are there any links users can visit to find out more?_
GitHub Security Advisory: GHSA-rvfh-h6c7-fc3c
Package: gradio (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-116: Improper Encoding or Escaping of Output
Vulnerable versions: < 4.20.0
Patched in: 4.20.0

Summary: Gradio allows credential leakage on Windows

Details:
Gradio before 4.20 allows credential leakage on Windows.