deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-4jvf-wx3f-2x8q
Package: aws_advanced_python_wrapper (PIP)
Severity: HIGH (CVSS 8.0)
CWE: CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Vulnerable versions: < 1.4.0
Patched in: 1.4.0

Summary: AWS Advanced Python Wrapper: Privilege Escalation in Aurora PostgreSQL instance 

Details:
### Description of Vulnerability:

An issue in AWS Wrappers for Amazon Aurora PostgreSQL may allow for privilege escalation to rds_superuser role. A low privilege authenticated user can create a crafted function that could be executed with permissions of other Amazon Relational Database Service (RDS) users.

AWS recommends customers upgrade to the following versions:  AWS Python Wrapper to v1.4.0


### Source of Vulnerability Report: 
Allistair Ishmael Hakim <allistair.hakim@gmail.com>


### Affected products & versions: 
AWS Python Wrapper < 1.4.0


### Platforms: 
MacOS/Windows/Linux
GitHub Security Advisory: GHSA-w2p4-p4rh-qcm3
Package: pgadmin4 (PIP)
Severity: CRITICAL (CVSS 9.1)
CWE: CWE-94: Improper Control of Generation of Code ('Code Injection')
Vulnerable versions: < 9.10
Patched in: 9.10

Summary: pgAdmin4 vulnerable to Remote Code Execution (RCE) when running in server mode

Details:
pgAdmin versions up to 9.9 are affected by a Remote Code Execution (RCE) vulnerability that occurs when running in server mode and performing restores from PLAIN-format dump files. This issue allows attackers to inject and execute arbitrary commands on the server hosting pgAdmin, posing a critical risk to the integrity and security of the database management system and underlying data.
GitHub Security Advisory: GHSA-rrx3-2x4g-mq2h
Package: bugsink (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: < 2.0.6
Patched in: 2.0.6

Summary: Bugsink is vulnerable to unauthenticated remote DoS via crafted Brotli input (via CPU)

Details:
### Impact

In affected versions, a specially crafted Brotli-compressed envelope can cause Bugsink to spend excessive CPU time in decompression, leading to denial of service.

This can be done if the DSN is known, which it is in many common setups (JavaScript, Mobile Apps).

### Patches

Patched in Bugsink 2.0.6

### References

The vulnerability in this security advisory is similar to, but distinct from, another brotli-related problem in Bugsink:

https://github.com/bugsink/bugsink/security/advisories/GHSA-fc2v-vcwj-269v
GitHub Security Advisory: GHSA-fc2v-vcwj-269v
Package: bugsink (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: < 2.0.5
Patched in: 2.0.5

Summary: Bugsink is vulnerable to unauthenticated remote DoS via crafted Brotli input

Details:
### Impact

In affected versions, brotli "bombs" (highly compressed brotli streams, such as many zeros) can be sent to the server. Since the server will attempt to decompress these streams before applying various maximums, this can lead to exhaustion of the available memory and thus a Denial of Service.

This can be done if the `DSN` is known, which it is in many common setups (JavaScript, Mobile Apps).

### Patches

Patched in Bugsink `2.0.5`
GitHub Security Advisory: GHSA-4c3j-3h7v-22q9
Package: changedetection.io (PIP)
Severity: LOW (CVSS 3.5)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: < 0.50.34
Patched in: 0.50.34

Summary: changedetection.io: Stored XSS in Watch update via API

Details:
### Summary

A Stored Cross Site Scripting is present in the changedetection.io Watch update API due to unsufficient security checks.

### Details

Tested on changedetection.io version *v0.50.24*

```console
REPOSITORY                            TAG       IMAGE ID       CREATED        SIZE
ghcr.io/dgtlmoon/changedetection.io   latest   [PII_REDACTED]a0   23 hours ago   599MB
```

When a user tries to add an unsafe URL as a Watch in the changedetection.io UI, the action is blocked with the error message "Watch protocol is not permitted by SAFE_PROTOCOL_REGEX or incorrect URL format".
This is catched by the function `validate_url(test_url)`.

```python
def validate_url(test_url):
    # ...
    from .model.Watch import is_safe_url
    if not is_safe_url(test_url):
        # This should be wtforms.validators.
        raise ValidationError('Watch protocol is not permitted by SAFE_PROTOCOL_REGEX or incorrect URL format')
```

When instead the Watch API is used, this check is not performed resulting in unsafe URLs added as Watch.

### PoC

Update an existing watch with an unsafe URL
```console
curl -X PUT "http://example.site/api/v1/watch/1242e1c5-d59e-4352-0078-203a55b21282" \
  -H "x-api-key: XXX" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "javascript:alert(document.domain)",
    "title": "XSS PoC",
    "paused": false
  }'
```

### Impact

Two scenarios are possibile:

1. An attacker can insert a new watch with an arbitrary URL which really points to a web page. Once the HTML content is retrieved, the attacker updates the URL with a JavaScript payload.
2. An attacker substitutes the URL in an existing watch with a new URL that is in reality a JavaScript payload.

When the user clicks on *Preview* and then on the malicious link, the JavaScript malicious code is executed.

<img width="1200" height="643" alt="poc1" src="https://github.com/user-attachments/assets/db81e0c7-b6d3-4332-b15d-a688a48c3227" />
<br>
<img width="1200" height="643" alt="poc2" src="https://github.com/user-attachments/assets/e704b37c-d339-4322-9fc0-ad50dd86b31d" />



### Credits

Edoardo Ottavianelli @edoardottt
GitHub Security Advisory: GHSA-vm2f-46xc-5jc3
Package: AstrBot (PIP)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), CWE-125: Out-of-bounds Read
Vulnerable versions: <= 3.5.22
Patched in: unpatched

Summary: AstrBot has an arbitrary file read vulnerability in function _encode_image_bs64

Details:
AstrBot Project v3.5.22 has an arbitrary file read vulnerability in function _encode_image_bs64. Since the _encode_image_bs64 function defined in entities.py opens the image specified by the user in the request body and returns the image content as a base64-encoded string without checking the legitimacy of the image path, attackers can construct a series of malicious URLs to read any specified file, resulting in sensitive data leakage.
GitHub Security Advisory: GHSA-xrj9-mw57-j34v
Package: AstrBot (PIP)
Severity: HIGH (CVSS 0.0)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: <= 3.5.22
Patched in: unpatched

Summary: AstrBot contains a directory traversal vulnerability

Details:
AstrBot Project v3.5.22 contains a directory traversal vulnerability. The handler function install_plugin_upload of the interface '/plugin/install-upload' parses the filename from the request body provided by the user, and directly uses the filename to assign to file_path without checking the validity of the filename. The variable file_path is then passed as a parameter to the function `file.save`, so that the file in the request body can be saved to any location in the file system through directory traversal.
GitHub Security Advisory: GHSA-w832-gg5g-x44m
Package: datasette (PIP)
Severity: LOW (CVSS 0.0)
CWE: CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Vulnerable versions: >= 1.0a0, < 1.0a20
Patched in: 1.0a21

Summary: Open redirect endpoint in Datasette

Details:
### Impact

Deployed instances of Datasette prior to `0.65.2` and `1.0a21` include an open redirect vulnerability.

Hits to the path `//example.com/foo/bar/` (the trailing slash is required) will redirect the user to `https://example.com/foo/bar`.

### Patches

This problem has been patched in both Datasette `0.65.2` and `1.0a21`.

### Workarounds

If Datasette is running behind a proxy that proxy could be configured to replace `//` with `/` in incoming request URLs.
GitHub Security Advisory: GHSA-w832-gg5g-x44m
Package: datasette (PIP)
Severity: LOW (CVSS 0.0)
CWE: CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Vulnerable versions: < 0.65.2
Patched in: 0.65.2

Summary: Open redirect endpoint in Datasette

Details:
### Impact

Deployed instances of Datasette prior to `0.65.2` and `1.0a21` include an open redirect vulnerability.

Hits to the path `//example.com/foo/bar/` (the trailing slash is required) will redirect the user to `https://example.com/foo/bar`.

### Patches

This problem has been patched in both Datasette `0.65.2` and `1.0a21`.

### Workarounds

If Datasette is running behind a proxy that proxy could be configured to replace `//` with `/` in incoming request URLs.
GitHub Security Advisory: GHSA-frmv-pr5f-9mcr
Package: django (PIP)
Severity: CRITICAL (CVSS 9.1)
CWE: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Vulnerable versions: < 4.2.26
Patched in: 4.2.26

Summary: Django vulnerable to SQL injection via _connector keyword argument in QuerySet and Q objects.

Details:
An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8.
The methods `QuerySet.filter()`, `QuerySet.exclude()`, and `QuerySet.get()`, and the class `Q()`, are subject to SQL injection when using a suitably crafted dictionary, with dictionary expansion, as the `_connector` argument.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank cyberstan for reporting this issue.
GitHub Security Advisory: GHSA-frmv-pr5f-9mcr
Package: django (PIP)
Severity: CRITICAL (CVSS 9.1)
CWE: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Vulnerable versions: >= 5.0a1, < 5.1.14
Patched in: 5.1.14

Summary: Django vulnerable to SQL injection via _connector keyword argument in QuerySet and Q objects.

Details:
An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8.
The methods `QuerySet.filter()`, `QuerySet.exclude()`, and `QuerySet.get()`, and the class `Q()`, are subject to SQL injection when using a suitably crafted dictionary, with dictionary expansion, as the `_connector` argument.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank cyberstan for reporting this issue.
GitHub Security Advisory: GHSA-frmv-pr5f-9mcr
Package: django (PIP)
Severity: CRITICAL (CVSS 9.1)
CWE: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Vulnerable versions: >= 5.2a1, < 5.2.8
Patched in: 5.2.8

Summary: Django vulnerable to SQL injection via _connector keyword argument in QuerySet and Q objects.

Details:
An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8.
The methods `QuerySet.filter()`, `QuerySet.exclude()`, and `QuerySet.get()`, and the class `Q()`, are subject to SQL injection when using a suitably crafted dictionary, with dictionary expansion, as the `_connector` argument.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank cyberstan for reporting this issue.
GitHub Security Advisory: GHSA-qw25-v68c-qjf3
Package: django (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-407: Inefficient Algorithmic Complexity
Vulnerable versions: < 4.2.26
Patched in: 4.2.26

Summary: Django has a denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows

Details:
An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8.
NFKC normalization in Python is slow on Windows. As a consequence, `django.http.HttpResponseRedirect`, `django.http.HttpResponsePermanentRedirect`, and the shortcut `django.shortcuts.redirect`  were subject to a potential  denial-of-service attack via certain inputs with a very large number of Unicode characters.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Seokchan Yoon for reporting this issue.
GitHub Security Advisory: GHSA-qw25-v68c-qjf3
Package: django (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-407: Inefficient Algorithmic Complexity
Vulnerable versions: >= 5.0a1, < 5.1.14
Patched in: 5.1.14

Summary: Django has a denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows

Details:
An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8.
NFKC normalization in Python is slow on Windows. As a consequence, `django.http.HttpResponseRedirect`, `django.http.HttpResponsePermanentRedirect`, and the shortcut `django.shortcuts.redirect`  were subject to a potential  denial-of-service attack via certain inputs with a very large number of Unicode characters.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Seokchan Yoon for reporting this issue.
GitHub Security Advisory: GHSA-qw25-v68c-qjf3
Package: django (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-407: Inefficient Algorithmic Complexity
Vulnerable versions: >= 5.2a1, < 5.2.8
Patched in: 5.2.8

Summary: Django has a denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows

Details:
An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8.
NFKC normalization in Python is slow on Windows. As a consequence, `django.http.HttpResponseRedirect`, `django.http.HttpResponsePermanentRedirect`, and the shortcut `django.shortcuts.redirect`  were subject to a potential  denial-of-service attack via certain inputs with a very large number of Unicode characters.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Seokchan Yoon for reporting this issue.
GitHub Security Advisory: GHSA-m35w-xx8c-6xc7
Package: doris-mcp-server (PIP)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-284: Improper Access Control
Vulnerable versions: < 0.6.0
Patched in: 0.6.0

Summary: Apache Doris-MCP-Server: Improper Access Control results in bypassing a "read-only" mode

Details:
An attacker with a valid read-only account can bypass Doris MCP Server’s read-only mode due to improper access control, allowing modifications that should have been prevented by read-only restrictions.

Impact:

Bypasses read-only mode; attackers with read-only access may perform unauthorized modifications.

Recommended action for operators: Upgrade to version 0.6.0 as soon as possible (this release contains the fix).
GitHub Security Advisory: GHSA-gr35-vpx2-qxhc
Package: weblate (PIP)
Severity: LOW (CVSS 2.6)
CWE: CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer
Vulnerable versions: < 5.14.1
Patched in: 5.14.1

Summary: Weblate leaks the IP of project member inviting user to be reviewer in Audit log

Details:
### Summary
Weblate leaks the IP address of the project member inviting the user to the project in the audit log.

### Details
The audit log included IP addresses from admin-triggered actions, and those could be viewed by invited users.

### Impact

The inviting user's (admin's) IP address could be leaked to invited users.
GitHub Security Advisory: GHSA-6xj8-rrqx-r4cv
Package: mlflow (PIP)
Severity: HIGH (CVSS 8.1)
CWE: CWE-521: Weak Password Requirements
Vulnerable versions: < 2.22.0rc0
Patched in: 2.22.0rc0

Summary: MLflow Weak Password Requirements Authentication Bypass Vulnerability

Details:
MLflow Weak Password Requirements Authentication Bypass Vulnerability. This vulnerability allows remote attackers to bypass authentication on affected installations of MLflow. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the handling of passwords. The issue results from weak password requirements. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-26916.
GitHub Security Advisory: GHSA-2qfp-q593-8484
Package: brotli (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: <= 1.1.0
Patched in: 1.2.0

Summary: Scrapy is vulnerable to a denial of service (DoS) attack due to flaws in brotli decompression implementation

Details:
Scrapy versions up to 2.13.3 are vulnerable to a denial of service (DoS) attack due to a flaw in its brotli decompression implementation. The protection mechanism against decompression bombs fails to mitigate the brotli variant, allowing remote servers to crash clients with less than 80GB of available memory. This occurs because brotli can achieve extremely high compression ratios for zero-filled data, leading to excessive memory consumption during decompression. Mitigation for this vulnerability needs security enhancement added in brotli v1.2.0.
GitHub Security Advisory: GHSA-vvw2-h478-xwr3
Package: dspy (PIP)
Severity: MODERATE (CVSS 5.9)
CWE: CWE-653: Improper Isolation or Compartmentalization
Vulnerable versions: <= 3.0.3
Patched in: unpatched

Summary: DSPy does not properly restrict file reads

Details:
The overly permissive sandbox configuration in DSPy allows attackers to steal sensitive files in cases when users build an AI agent which consumes user input and uses the “PythonInterpreter” class.
GitHub Security Advisory: GHSA-crvm-xjhm-9h29
Package: octoprint (PIP)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), CWE-80: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)
Vulnerable versions: <= 1.11.3
Patched in: 1.11.4

Summary: OctoPrint vulnerable to XSS in Action Commands Notification and Prompt

Details:
### Impact

OctoPrint versions up to and including 1.11.3 are affected by a vulnerability that allows injection of arbitrary HTML and JavaScript into Action Command notification and prompt popups generated by the printer.

An attacker who successfully convinces a victim to print a specially crafted file could exploit this issue to disrupt ongoing prints, extract information (including sensitive configuration settings, if the targeted user has the necessary permissions for that), or perform other actions on behalf of the targeted user within the OctoPrint instance.

### Patches

The vulnerability will be patched in version 1.11.4.

### Workaround

OctoPrint administrators can mitigate the risk by disabling popups:
- for Action Command notifications, uncheck _OctoPrint Settings -> Printer Notifications -> Enable popups_
- for Action Command prompts, set _OctoPrint Settings -> Printer Dialogs -> Enable support -> Never_

It is also strongly recommended to ensure that files being printed originate from trusted sources, and, whenever possible, are sliced with your own slicer.

### Credits

This vulnerability was discovered and responsibly disclosed to OctoPrint by [Jacopo Tediosi](https://github.com/jacopotediosi).
GitHub Security Advisory: GHSA-4vcx-3pj3-44m7
Package: dosage (PIP)
Severity: HIGH (CVSS 8.8)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: < 3.2
Patched in: 3.2

Summary: Dosage vulnerable to a Directory Traversal through crafted HTTP responses

Details:
### Impact

When downloadinging comic images, Dosage constructs target file names from different aspects of the remote comic (page URL, image URL, page content, etc.). While the basename is properly stripped of directory-traversing characters, the file extension is taken from the HTTP `Content-Type` header. This allows a remote attacker (or a Man-in-the-Middle, if the comic is served over HTTP) to write arbitrary files outside the target directory (if additional conditions are met). 

### Patches

Fixed in release 3.2. The [fix is small and self-contained](https://github.com/webcomics/dosage/commit/336a[PII_REDACTED]bc49eed7296b74bd582151181e), so distributors might elect to backport the fix to older versions.

### Workarounds

No
GitHub Security Advisory: GHSA-26f6-wm47-7h7j
Package: motioneye (PIP)
Severity: HIGH (CVSS 7.2)
CWE: CWE-20: Improper Input Validation
Vulnerable versions: < 0.43.1b5
Patched in: unpatched

Summary: Duplicate Advisory: motionEye vulnerable to RCE via unsanitized motion config parameter

Details:
## Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-j945-qm58-4gjx. This link is maintained to preserve external references.

## Original Description
MotionEye v0.43.1b4 and before is vulnerable to OS Command Injection in configuration parameters such as image_file_name. Unsanitized user input is written to Motion configuration files, allowing remote authenticated attackers with admin access to achieve code execution when Motion is restarted.
GitHub Security Advisory: GHSA-8v8h-4pjx-rg73
Package: langchain-chatchat (PIP)
Severity: LOW (CVSS 4.3)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: <= 0.3.1
Patched in: unpatched

Summary: Langchain-Chatchat vulnerable to path traversal

Details:
A vulnerability classified as problematic was found in chatchat-space Langchain-Chatchat up to 0.3.1. This vulnerability affects unknown code of the file /v1/files?purpose=assistants. The manipulation leads to path traversal. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.
GitHub Security Advisory: GHSA-f823-phmg-x5fr
Package: langchain-chatchat (PIP)
Severity: LOW (CVSS 5.5)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: <= 0.3.1
Patched in: unpatched

Summary: Langchain-Chatchat vulnerable to path traversal

Details:
A vulnerability, which was classified as critical, has been found in chatchat-space Langchain-Chatchat up to 0.3.1. This issue affects some unknown processing of the file /v1/file. The manipulation of the argument flag leads to path traversal. The exploit has been disclosed to the public and may be used.
GitHub Security Advisory: GHSA-vw84-hprm-cxmm
Package: agno (PIP)
Severity: HIGH (CVSS 7.1)
CWE: CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'), CWE-668: Exposure of Resource to Wrong Sphere
Vulnerable versions: >= 2.0.0, < 2.2.2
Patched in: 2.2.2

Summary: Agno session state overwrites between different sessions/users

Details:
### Impact
Under certain conditions (under high concurrency), when `session_state` is passed to an Agent or Team during run or arun calls, a race condition can occur, causing a `session_state` to be assigned and persisted to the incorrect session. This may result in user data from one session being exposed to another user.

### Patches
This has been patched in version 2.2.2. Upgrade with `pip install -U agno`.
GitHub Security Advisory: GHSA-97w9-v595-3h5q
Package: cryptidy (PIP)
Severity: MODERATE (CVSS 6.9)
CWE: CWE-502: Deserialization of Untrusted Data
Vulnerable versions: <= 1.2.4
Patched in: unpatched

Summary: cryptidy allows code execution via untrusted data due to pickle.loads 

Details:
cryptidy through 1.2.4 allows code execution via untrusted data because pickle.loads is used. This occurs in aes_decrypt_message in symmetric_encryption.py.