netbird/advisory-database
0
0
Fork 0
mirror of https://github.com/netbirdio/advisory-database.git synced 2026-05-22 18:04:22 -07:00
Code Issues Packages Projects Releases Wiki Activity

Publish Advisories

Browse Source 
GHSA-fqxj-46wg-9v84
GHSA-x9xc-63hg-vcfq
This commit is contained in:
advisory-database[bot]
2025-04-01 23:01:30 +00:00
parent 8553b76b57
commit fe50ba600e
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
advisories/github-reviewed/2024/02/GHSA-fqxj-46wg-9v84/GHSA-fqxj-46wg-9v84.json
+2 -2
View File
@@ -1,13 +1,13 @@
{
"schema_version": "1.4.0",
"id": "GHSA-fqxj-46wg-9v84",
"modified": "2024-03-01T14:54:32Z",
"modified": "2025-04-01T22:59:33Z",
"published": "2024-02-28T18:37:01Z",
"aliases": [
"CVE-2024-27083"
],
"summary": "Flask-AppBuilder's OAuth login page subject to Cross Site Scripting (XSS)",
"details": "### Impact\nA Cross-Site Scripting (XSS) vulnerability has been discovered on the OAuth login page. An attacker could trick a user to follow a specially crafted URL to the OAuth login page. This URL could inject and execute malicious javascript code that would get executed on the user's browser.\n\nImpacted versions:\nFlask-AppBuilder version 4.1.4 up to and including 4.2.0\n\n### Patches\nThis issue was introduced on 4.1.4 and patched on 4.2.1, user's should upgrade to 4.2.1 or newer versions.\n",
"details": "### Impact\nA Cross-Site Scripting (XSS) vulnerability has been discovered on the OAuth login page. An attacker could trick a user to follow a specially crafted URL to the OAuth login page. This URL could inject and execute malicious javascript code that would get executed on the user's browser.\n\nImpacted versions:\nFlask-AppBuilder version 4.1.4 up to and including 4.2.0\n\n### Patches\nThis issue was introduced on 4.1.4 and patched on 4.2.1, user's should upgrade to 4.2.1 or newer versions.",
"severity": [
{
"type": "CVSS_V3",
advisories/github-reviewed/2024/04/GHSA-x9xc-63hg-vcfq/GHSA-x9xc-63hg-vcfq.json
+2 -2
View File
@@ -1,13 +1,13 @@
{
"schema_version": "1.4.0",
"id": "GHSA-x9xc-63hg-vcfq",
"modified": "2024-04-05T15:00:55Z",
"modified": "2025-04-01T22:59:42Z",
"published": "2024-04-05T15:00:55Z",
"aliases": [
"CVE-2024-27284"
],
"summary": "cassandra-rs's non-idiomatic use of iterators leads to use after free",
"details": "### Impact\nCode that attempts to use an item (e.g., a row) returned by an iterator after the iterator has advanced to the next item will be accessing freed memory and experience undefined behaviour. Code that uses the item and then advances the iterator is unaffected. This problem has always existed.\n\nThis is a use-after-free bug, so it's rated high severity. If your code uses a pre-3.0.0 version of cassandra-rs, and uses an item returned by a cassandra-rs iterator after calling `next()` on that iterator, then it is vulnerable. However, such code will almost always fail immediately - so we believe it is unlikely that any code using this pattern would have reached production. For peace of mind, we recommend you upgrade anyway.\n\n### Patches\nThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern.\n\n### Workarounds\nEnsure all usage fits the expected pattern. For example, use `get_first_row()` rather than an iterator, or completely process an item before advancing the iterator with `next()`.\n\n### References\nNone.\n",
"details": "### Impact\nCode that attempts to use an item (e.g., a row) returned by an iterator after the iterator has advanced to the next item will be accessing freed memory and experience undefined behaviour. Code that uses the item and then advances the iterator is unaffected. This problem has always existed.\n\nThis is a use-after-free bug, so it's rated high severity. If your code uses a pre-3.0.0 version of cassandra-rs, and uses an item returned by a cassandra-rs iterator after calling `next()` on that iterator, then it is vulnerable. However, such code will almost always fail immediately - so we believe it is unlikely that any code using this pattern would have reached production. For peace of mind, we recommend you upgrade anyway.\n\n### Patches\nThe problem has been fixed in version 3.0.0. Users should upgrade to ensure their code cannot use the problematic pattern.\n\n### Workarounds\nEnsure all usage fits the expected pattern. For example, use `get_first_row()` rather than an iterator, or completely process an item before advancing the iterator with `next()`.\n\n### References\nNone.",
"severity": [
{
"type": "CVSS_V3",