deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-832w-fhmw-w4f4
Package: dtale (PIP)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: < 3.16.1
Patched in: 3.16.1

Summary: D-Tale allows Remote Code Execution through the Custom Filter Input

Details:
### Impact
Users hosting D-Tale publicly can be vulnerable to remote code execution allowing attackers to run malicious code on the server.

### Patches
Users should upgrade to version 3.16.1 where the `update-settings` endpoint blocks the ability for users to update the `enable_custom_filters` flag. You can find out more information on how to turn that flag on [here](https://github.com/man-group/dtale#custom-filter)

### Workarounds
The only workaround for versions earlier than 3.16.1 is to only host D-Tale to trusted users.

### References
See "Custom Filter" [documentation](https://github.com/man-group/dtale#custom-filter)
GitHub Security Advisory: GHSA-787v-v9vq-4rgv
Package: apache-superset (PIP)
Severity: HIGH (CVSS 6.5)
CWE: CWE-285: Improper Authorization, CWE-863: Incorrect Authorization
Vulnerable versions: < 4.1.0
Patched in: 4.1.0

Summary: Apache Superset: SQLLab Improper readonly query validation allows unauthorized write access

Details:
Improper Authorization vulnerability in Apache Superset. On Postgres analytic databases an attacker with SQLLab access can craft a specially designed SQL DML statement that is Incorrectly identified as a read-only query, enabling its execution. Non postgres analytics database connections and postgres analytics database connections set with a readonly user (advised) are not vulnerable. 

This issue affects Apache Superset: before 4.1.0.

Users are recommended to upgrade to version 4.1.0, which fixes the issue.
GitHub Security Advisory: GHSA-75mx-hw5q-pvx3
Package: python-libarchive (PIP)
Severity: HIGH (CVSS 8.8)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: <= 4.2.1
Patched in: unpatched

Summary: python-libarchive directory traversal

Details:
python-libarchive through 4.2.1 allows directory traversal (to create files) in extract in zip.py for ZipFile.extractall and ZipFile.extract.
GitHub Security Advisory: GHSA-pqj8-xhcx-prxm
Package: pyspider (PIP)
Severity: HIGH (CVSS 8.8)
CWE: CWE-352: Cross-Site Request Forgery (CSRF)
Vulnerable versions: <= 0.3.10
Patched in: unpatched

Summary: pyspider Cross-Site Request Forgery (CSRF) via the Flask endpoints

Details:
binux pyspider up to v0.3.10 was discovered to contain a Cross-Site Request Forgery (CSRF) via the Flask endpoints.
GitHub Security Advisory: GHSA-hhfg-fwrw-87w7
Package: sigstore (PIP)
Severity: LOW (CVSS 0.0)
CWE: CWE-20: Improper Input Validation, CWE-325: Missing Cryptographic Step
Vulnerable versions: >= 2.0.0, < 3.6.0
Patched in: 3.6.0

Summary: sigstore has insufficient validation of integration timestamp during verification

Details:
### Summary

Versions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified *if* a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present.

This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise.

### Details

Sigstore uses signed time to support verification of signatures made against short-lived signing keys. 

### Impact

The impact and severity of this weakness is *low*, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify).

Separately, an attacker could upload a *new* entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable.
GitHub Security Advisory: GHSA-8qch-vj6m-2694
Package: luigi (PIP)
Severity: HIGH (CVSS 8.6)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), CWE-29: Path Traversal: '..filename'
Vulnerable versions: < 3.6.0
Patched in: 3.6.0

Summary: luigi Arbitrary File Write via Archive Extraction (Zip Slip)

Details:
Versions of the package luigi before 3.6.0 are vulnerable to Arbitrary File Write via Archive Extraction (Zip Slip) due to improper destination file path validation in the _extract_packages_archive function.
GitHub Security Advisory: GHSA-32r8-54hf-c9p3
Package: unstructured (PIP)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-611: Improper Restriction of XML External Entity Reference
Vulnerable versions: < 0.14.3
Patched in: 0.14.3

Summary: unstructured XML External Entity (XXE)

Details:
unstructured v.0.14.2 and before is vulnerable to XML External Entity (XXE) via the XMLParser.
GitHub Security Advisory: GHSA-92qf-8gh3-gwcm
Package: apache-superset (PIP)
Severity: LOW (CVSS 9.8)
CWE: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Vulnerable versions: < 4.1.0
Patched in: 4.1.0

Summary: Apache Superset: Improper SQL authorisation, parse not checking for specific postgres functions

Details:
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache Superset. Specifically, certain engine-specific functions are not checked, which allows attackers to bypass Apache Superset's SQL authorization. This issue is a follow-up to CVE-2024-39887 with additional disallowed PostgreSQL functions now included: query_to_xml_and_xmlschema, table_to_xml, table_to_xml_and_xmlschema.

This issue affects Apache Superset: <4.1.0.

Users are recommended to upgrade to version 4.1.0, which fixes the issue or add these Postgres functions to the config set DISALLOWED_SQL_FUNCTIONS.
GitHub Security Advisory: GHSA-35fc-9hrj-3585
Package: apache-superset (PIP)
Severity: HIGH (CVSS 6.5)
CWE: CWE-285: Improper Authorization, CWE-863: Incorrect Authorization
Vulnerable versions: >= 2.0.0, < 4.1.0
Patched in: 4.1.0

Summary: Apache Superset: Lower privilege users are able to create Role when FAB_ADD_SECURITY_API is enabled

Details:
Improper Authorization vulnerability in Apache Superset when FAB_ADD_SECURITY_API is enabled (disabled by default). Allows for lower privilege users to use this API.

 issue affects Apache Superset: from 2.0.0 before 4.1.0.

Users are recommended to upgrade to version 4.1.0, which fixes the issue.
GitHub Security Advisory: GHSA-2cx9-54hp-r698
Package: apache-superset (PIP)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-209: Generation of Error Message Containing Sensitive Information
Vulnerable versions: < 4.1.0
Patched in: 4.1.0

Summary: Apache Superset: Error verbosity exposes metadata in analytics databases

Details:
Generation of Error Message Containing analytics metadata Information in Apache Superset.

This issue affects Apache Superset: before 4.1.0.

Users are recommended to upgrade to version 4.1.0, which fixes the issue.
GitHub Security Advisory: GHSA-m9g8-fxxm-xg86
Package: Django (PIP)
Severity: HIGH (CVSS 9.8)
CWE: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Vulnerable versions: >= 4.2.0, < 4.2.17
Patched in: 4.2.17

Summary: Django SQL injection in HasKey(lhs, rhs) on Oracle

Details:
An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. Direct usage of the django.db.models.fields.json.HasKey lookup, when an Oracle database is used, is subject to SQL injection if untrusted data is used as an lhs value. (Applications that use the jsonfield.has_key lookup via __ are unaffected.)
GitHub Security Advisory: GHSA-m9g8-fxxm-xg86
Package: Django (PIP)
Severity: HIGH (CVSS 9.8)
CWE: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Vulnerable versions: >= 5.1.0, < 5.1.4
Patched in: 5.1.4

Summary: Django SQL injection in HasKey(lhs, rhs) on Oracle

Details:
An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. Direct usage of the django.db.models.fields.json.HasKey lookup, when an Oracle database is used, is subject to SQL injection if untrusted data is used as an lhs value. (Applications that use the jsonfield.has_key lookup via __ are unaffected.)
GitHub Security Advisory: GHSA-m9g8-fxxm-xg86
Package: Django (PIP)
Severity: HIGH (CVSS 9.8)
CWE: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Vulnerable versions: >= 5.0.0, < 5.0.10
Patched in: 5.0.10

Summary: Django SQL injection in HasKey(lhs, rhs) on Oracle

Details:
An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. Direct usage of the django.db.models.fields.json.HasKey lookup, when an Oracle database is used, is subject to SQL injection if untrusted data is used as an lhs value. (Applications that use the jsonfield.has_key lookup via __ are unaffected.)
GitHub Security Advisory: GHSA-8498-2h75-472j
Package: Django (PIP)
Severity: MODERATE (CVSS 7.5)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: >= 5.0.0, < 5.0.10
Patched in: 5.0.10

Summary: Django denial-of-service in django.utils.html.strip_tags()

Details:
An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. The strip_tags() method and striptags template filter are subject to a potential denial-of-service attack via certain inputs containing large sequences of nested incomplete HTML entities.
GitHub Security Advisory: GHSA-8498-2h75-472j
Package: Django (PIP)
Severity: MODERATE (CVSS 7.5)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: >= 4.2.0, < 4.2.17
Patched in: 4.2.17

Summary: Django denial-of-service in django.utils.html.strip_tags()

Details:
An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. The strip_tags() method and striptags template filter are subject to a potential denial-of-service attack via certain inputs containing large sequences of nested incomplete HTML entities.
GitHub Security Advisory: GHSA-8498-2h75-472j
Package: Django (PIP)
Severity: MODERATE (CVSS 7.5)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: >= 5.1.0, < 5.1.4
Patched in: 5.1.4

Summary: Django denial-of-service in django.utils.html.strip_tags()

Details:
An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. The strip_tags() method and striptags template filter are subject to a potential denial-of-service attack via certain inputs containing large sequences of nested incomplete HTML entities.
GitHub Security Advisory: GHSA-99w6-3xph-cx78
Package: ansible-core (PIP)
Severity: LOW (CVSS 5.5)
CWE: CWE-20: Improper Input Validation
Vulnerable versions: < 2.16.14rc1
Patched in: 2.16.14rc1

Summary: Ansible-Core vulnerable to content protections bypass

Details:
A flaw was found in Ansible-Core. This vulnerability allows attackers to bypass unsafe content protections using the hostvars object to reference and execute templated content. This issue can lead to arbitrary code execution if remote data or module outputs are improperly templated within playbooks.
GitHub Security Advisory: GHSA-99w6-3xph-cx78
Package: ansible-core (PIP)
Severity: LOW (CVSS 5.5)
CWE: CWE-20: Improper Input Validation
Vulnerable versions: >= 2.17.0b1, < 2.17.7rc1
Patched in: 2.17.7rc1

Summary: Ansible-Core vulnerable to content protections bypass

Details:
A flaw was found in Ansible-Core. This vulnerability allows attackers to bypass unsafe content protections using the hostvars object to reference and execute templated content. This issue can lead to arbitrary code execution if remote data or module outputs are improperly templated within playbooks.
GitHub Security Advisory: GHSA-99w6-3xph-cx78
Package: ansible-core (PIP)
Severity: LOW (CVSS 5.5)
CWE: CWE-20: Improper Input Validation
Vulnerable versions: >= 2.18.0b1, < 2.18.1rc1
Patched in: 2.18.1rc1

Summary: Ansible-Core vulnerable to content protections bypass

Details:
A flaw was found in Ansible-Core. This vulnerability allows attackers to bypass unsafe content protections using the hostvars object to reference and execute templated content. This issue can lead to arbitrary code execution if remote data or module outputs are improperly templated within playbooks.
GitHub Security Advisory: GHSA-v5h2-q2w4-gpcx
Package: sentry (PIP)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-209: Generation of Error Message Containing Sensitive Information
Vulnerable versions: = 24.11.0
Patched in: 24.11.1

Summary: Sentry improper error handling leaks Application Integration Client Secret

Details:
### Impact
During routine testing, we identified a scenario where a specific error message generated by our platform could include a plaintext Client ID and Client Secret for an application integration. The Client ID and Client Secret would not be displayed in the UI, but would be returned in the underlying HTTP response to the end user. This could occur under the following conditions:
- An app installation made use of a [Search UI component](https://docs.sentry.io/organization/integrations/integration-platform/ui-components/formfield/#select) with the `async` flag set to true (default: true),
- A user types types into the Search Component which creates a request to the third-party for search or query results, and
- That third-party response may then fail validation and Sentry would return the `select-requester.invalid-response` error code along with a serialized version of a Sentry application containing the integration Client Secret.

Should this error be found, it's reasonable to assume the potential exposure of an integration Client Secret. However, an ID and Secret pair alone does not provide direct access to any data. For that secret to be abused an attacker would also need to obtain a valid API token for a Sentry application. 

#### Impact for SaaS Users
For Sentry SaaS users, we have confirmed that only a single application integration was impacted and the owner has rotated their Client Secret. We have also confirmed that no abuse of the leaked Client Secret has occurred. 

#### Potential Impact for Self-Hosted Users
Sentry self-hosted does not ship with any application integrations. This could only impact self-hosted users that maintain their own integrations. In that case, search for a `select-requester.invalid-response` event. Please note that this error was also shared with another event unrelated to this advisory so you will also need to review the parameters logged for each named event. You may review [select_requester.py](https://github.com/getsentry/sentry/blob/4a448fbb0d0b416fef9ee0ab26579e0dc16f21b7/src/sentry/sentry_apps/external_requests/select_requester.py#L78-L123) for the instances where these errors can be generated. With the security fix this is no longer a shared event type.

### Patches
- Sentry SaaS users do not need to take any action.
- Sentry self-hosted users should upgrade to 24.11.1 or higher.

### References
- Bug introduced in https://github.com/getsentry/sentry/pull/79377
- Security fix in https://github.com/getsentry/sentry/pull/81038
GitHub Security Advisory: GHSA-5jc6-h9w7-jm3p
Package: mobsf (PIP)
Severity: MODERATE (CVSS 6.1)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: < 4.2.9
Patched in: 4.2.9

Summary: Mobile Security Framework (MobSF) Stored Cross-Site Scripting Vulnerability in "Diff or Compare" Functionality

Details:
### Summary
The application allows users to upload files with scripts in the filename parameter. As a result, a malicious user can upload a script file to the system. When users in the application use the "Diff or Compare" functionality, they are affected by a Stored Cross-Site Scripting vulnerability.

### Details
I found a Stored Cross-Site Scripting vulnerability in the "Diff or Compare" functionality. This issue occurs because the upload functionality allows users to upload files with special characters such as <, >, /, and " in the filename. This vulnerability can be mitigated by restricting file uploads to filenames containing only whitelisted characters, such as A-Z, 0-9, and specific special characters permitted by business requirements, like - or _ . 

### PoC
_Complete instructions, including specific configuration details, to reproduce the vulnerability._
1. On MobSF version 4.2.8, I clicked on "Unload & Analyze" button.
![0](https://github.com/user-attachments/assets/489013fe-cf21-4839-bd39-35eebad01a3a)

2. I uploaded zip file as a name `test.zip`.
![1](https://github.com/user-attachments/assets/c26a18ec-c276-43d5-97df-fb189b8d5a6a)

3. I used an intercepting proxy tool while uploading a file and changed the value of the filename parameter from `test.zip` to `<image src onerror=prompt(document.domain)>test.zip`. This means I uploaded a file and set its name to a script value. As a result, the server allowed the file to be uploaded successfully.
![2](https://github.com/user-attachments/assets/90e275a2-58a4-4c0d-9b6a-399ec071cdf2)

4. I accessed /recent_scans/ and found a file named `<image src onerror=prompt(document.domain)>test.zip` in the recent scans. Then, I clicked on the "Differ or Compare" button."
![3](https://github.com/user-attachments/assets/0997a437-5841-49c1-ae94-e0e76173bdb6)

5. I found that the application requires selecting a file to compare, and I selected the file `<image src onerror=prompt(document.domain)>test.zip`
![4](https://github.com/user-attachments/assets/a156f058-732f-4763-8753-b0cef4075d53)

6. I found that the JavaScript in the filename value was executed in the web browser.
![5](https://github.com/user-attachments/assets/b0a9bcbf-af70-4ec6-a22d-6224dfc55639)


### Impact
Allowing a malicious user to upload a script in the filename parameter can be used to steal information from other users or administrators when they perform the compare functionality. The script will be stored in the system permanently in this vulnerability.
GitHub Security Advisory: GHSA-56w4-5538-8v8h
Package: matrix-synapse (PIP)
Severity: MODERATE (CVSS 4.3)
CWE: CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere
Vulnerable versions: >= 1.113.0rc1, < 1.120.1
Patched in: 1.120.1

Summary: Synapse Matrix has a partial room state leak via Sliding Sync

Details:
### Impact
The Sliding Sync feature on Synapse versions between 1.113.0rc1 and 1.120.0 can leak partial room state changes to users no longer in a room. Non-state events, like messages, are unaffected.

### Patches
Synapse version 1.120.1 fixes the problem.

### Workarounds
Disable Sliding Sync.

### References
https://github.com/matrix-org/matrix-spec-proposals/pull/4186
https://github.com/element-hq/synapse/blob/d80cd57c54427687afcb48740d99219c88a0fff1/synapse/config/experimental.py#L341-L344

### For more information

If you have any questions or comments about this advisory, please email us at [security at element.io](mailto:security@element.io).
GitHub Security Advisory: GHSA-vp6v-whfm-rv3g
Package: matrix-synapse (PIP)
Severity: HIGH (CVSS 0.0)
CWE: CWE-434: Unrestricted Upload of File with Dangerous Type
Vulnerable versions: < 1.120.1
Patched in: 1.120.1

Summary: Synapse can be forced to thumbnail unexpected file formats, invoking external, potentially untrustworthy decoders

Details:
### Impact

In Synapse versions before 1.120.1, enabling the `dynamic_thumbnails` option or processing a specially crafted request could trigger the decoding and thumbnail generation of uncommon image formats, potentially invoking external tools like Ghostscript for processing.

This significantly expands the attack surface in a historically vulnerable area, presenting a risk that far outweighs the benefit, particularly since these formats are rarely used on the open web or within the Matrix ecosystem.

For a list of image formats, as well as decoding libraries and helper programs used, see [the Pillow documentation](https://pillow.readthedocs.io/en/stable/handbook/image-file-formats.html).

### Patches

Synapse 1.120.1 addresses the issue by restricting thumbnail generation to images in the following widely used formats: PNG, JPEG, GIF, and WebP.

### Workarounds

- Ensure any image codecs and helper programs, such as Ghostscript, are patched against security vulnerabilities.
- Uninstall unused image decoder libraries and helper programs, such as Ghostscript, from the system environment that Synapse is running in.
    - Depending on the installation method, there may be some decoder libraries bundled with Pillow and these cannot be easily uninstalled.
    - The official Docker container image does not include Ghostscript.

### References

- [The Pillow documentation](https://pillow.readthedocs.io/en/stable/handbook/image-file-formats.html) includes a list of supported image formats and which libraries or helper programs are used to decode them.

### For more information

If you have any questions or comments about this advisory, please email us at [security at element.io](mailto:security@element.io).
GitHub Security Advisory: GHSA-f3r3-h2mq-hx2h
Package: matrix-synapse (PIP)
Severity: HIGH (CVSS 0.0)
CWE: CWE-20: Improper Input Validation
Vulnerable versions: < 1.120.1
Patched in: 1.120.1

Summary: Synapse allows a a malformed invite to break the invitee's `/sync`

Details:
### Impact

Synapse versions before 1.120.1 fail to properly validate invites received over federation. This vulnerability allows a malicious server to send a specially crafted invite that disrupts the invited user's `/sync` functionality.

### Patches

Synapse 1.120.1 rejects such invalid invites received over federation and restores the ability to sync for affected users.

### Workarounds

Server administrators can disable federation from untrusted servers.

### For more information

If you have any questions or comments about this advisory, please email us at [security at element.io](mailto:security@element.io).
GitHub Security Advisory: GHSA-rfq8-j7rh-8hf2
Package: matrix-synapse (PIP)
Severity: HIGH (CVSS 0.0)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: < 1.120.1
Patched in: 1.120.1

Summary: Synapse allows unsupported content types to lead to memory exhaustion

Details:
### Impact

In Synapse before 1.120.1, `multipart/form-data` requests can in certain configurations transiently increase memory consumption beyond expected levels while processing the request, which can be used to amplify denial of service attacks.

### Patches

Synapse 1.120.1 resolves the issue by denying requests with unsupported `multipart/form-data` content type.

### Workarounds

Limiting request sizes or blocking the `multipart/form-data` content type before the requests reach Synapse, for example in a reverse proxy, alleviates the issue. Another approach that mitigates the attack is to use a low `max_upload_size` in Synapse.

### References

- https://github.com/twisted/twisted/issues/4688#issuecomment[PII_REDACTED]
- https://github.com/twisted/twisted/issues/4688#issuecomment[PII_REDACTED]

### For more information

If you have any questions or comments about this advisory, please email us at [security at element.io](mailto:security@element.io).