Publish Advisories

GHSA-gmrf-99gw-vvwj
GHSA-6r7c-6w96-8pvw
GHSA-74r6-grj9-8rq6
GHSA-89p3-9j8c-fqh4
GHSA-3f95-mxq2-2f63
GHSA-m842-4qm8-7gpq

Author: advisory-database[bot]

advisories/github-reviewed/2021/03/GHSA-gmrf-99gw-vvwj/GHSA-gmrf-99gw-vvwj.json

@@ -1,12 +1,19 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-gmrf-99gw-vvwj",
-  "modified": "2021-03-11T17:41:49Z",
+  "modified": "2026-02-03T17:38:56Z",
   "published": "2021-03-11T17:42:08Z",
-  "aliases": [],
+  "aliases": [
+    "CVE-2021-46876"
+  ],
   "summary": "/user/sessions endpoint allows detecting valid accounts",
   "details": "This Security Advisory is about a vulnerability in eZ Platform v1.13, v2.5, and v3.2, and in Ibexa DXP and Ibexa Open Source v3.3. The /user/sessions endpoint can let an attacker detect if a given username or email refers to a valid account. This can be detected through differences in the response data or response time of certain requests. The fix ensures neither attack is possible. The fix is distributed via Composer.\n\nIf you come across a security issue in our products, here is how you can report it to us: https://doc.ibexa.co/en/latest/guide/reporting_issues/#toc",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N"
+    }
+  ],
   "affected": [
     {
       "package": {
@@ -58,10 +65,18 @@
       "type": "WEB",
       "url": "https://github.com/ezsystems/ezpublish-kernel/security/advisories/GHSA-gmrf-99gw-vvwj"
     },
+    {
+      "type": "ADVISORY",
+      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-46876"
+    },
     {
       "type": "WEB",
       "url": "https://github.com/ezsystems/ezpublish-kernel/commit/b496f073c3f03707d3531a6941dc098b84e3cbed"
     },
+    {
+      "type": "PACKAGE",
+      "url": "https://github.com/ezsystems/ezpublish-kernel"
+    },
     {
       "type": "WEB",
       "url": "https://packagist.org/packages/ezsystems/ezpublish-kernel"
@@ -71,7 +86,7 @@
     "cwe_ids": [
       "CWE-203"
     ],
-    "severity": "HIGH",
+    "severity": "MODERATE",
     "github_reviewed": true,
     "github_reviewed_at": "2021-03-11T17:41:49Z",
     "nvd_published_at": null

advisories/github-reviewed/2021/12/GHSA-6r7c-6w96-8pvw/GHSA-6r7c-6w96-8pvw.json

@@ -1,11 +1,13 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-6r7c-6w96-8pvw",
-  "modified": "2022-01-04T18:56:03Z",
+  "modified": "2026-02-03T17:39:24Z",
   "published": "2021-12-07T21:21:49Z",
-  "aliases": [],
+  "aliases": [
+    "CVE-2021-23758"
+  ],
   "summary": "Remote Code Execution in AjaxNetProfessional",
-  "details": "### Overview\n\nAffected versions of this package are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary .NET classes, which can be abused to gain remote code execution.\n\n### Description\n\nSerialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.\n\nDeserialization of untrusted data (CWE-502), is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, letting the attacker to control the state or the flow of the execution.\n\nJava deserialization issues have been known for years. However, interest in the issue intensified greatly in 2015, when classes that could be abused to achieve remote code execution were found in a popular library (Apache Commons Collection). These classes were used in zero-days affecting IBM WebSphere, Oracle WebLogic and many other products.\n\nAn attacker just needs to identify a piece of software that has both a vulnerable class on its path, and performs deserialization on untrusted data. Then all they need to do is send the payload into the deserializer, getting the command executed.\n\nDevelopers put too much trust in Java Object Serialization. Some even de-serialize objects pre-authentication. When deserializing an Object in Java you typically cast it to an expected type, and therefore Java's strict type system will ensure you only get valid object trees. Unfortunately, by the time the type checking happens, platform code has already created and executed significant logic. So, before the final type is checked a lot of code is executed from the readObject() methods of various objects, all of which is out of the developer's control. By combining the readObject() methods of various classes which are available on the classpath of the vulnerable application an attacker can execute functions (including calling Runtime.exec() to execute local OS commands).\n\n### Releases\n\nReleases before version 21.11.29.1 are affected. Please be careful to download any binary DLL from other web sites, especially we found NuGet packages not owned by us that contain vulnerable versions.\n\n### Workarounds\n\nThere is no workaround available that addresses all issues except updating to latest version from GitHub.\n\n### References\n\nFind original CVE posting here: https://security.snyk.io/vuln/SNYK-DOTNET-AJAXPRO2-1925971\n\nNote: the official Ajax.NET Professional (AjaxPro) NuGet package is available here: https://www.nuget.org/packages/AjaxNetProfessional/\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue on this GitHub repository\n",
+  "details": "### Overview\n\nAffected versions of this package are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary .NET classes, which can be abused to gain remote code execution.\n\n### Description\n\nSerialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.\n\nDeserialization of untrusted data (CWE-502), is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, letting the attacker to control the state or the flow of the execution.\n\nJava deserialization issues have been known for years. However, interest in the issue intensified greatly in 2015, when classes that could be abused to achieve remote code execution were found in a popular library (Apache Commons Collection). These classes were used in zero-days affecting IBM WebSphere, Oracle WebLogic and many other products.\n\nAn attacker just needs to identify a piece of software that has both a vulnerable class on its path, and performs deserialization on untrusted data. Then all they need to do is send the payload into the deserializer, getting the command executed.\n\nDevelopers put too much trust in Java Object Serialization. Some even de-serialize objects pre-authentication. When deserializing an Object in Java you typically cast it to an expected type, and therefore Java's strict type system will ensure you only get valid object trees. Unfortunately, by the time the type checking happens, platform code has already created and executed significant logic. So, before the final type is checked a lot of code is executed from the readObject() methods of various objects, all of which is out of the developer's control. By combining the readObject() methods of various classes which are available on the classpath of the vulnerable application an attacker can execute functions (including calling Runtime.exec() to execute local OS commands).\n\n### Releases\n\nReleases before version 21.11.29.1 are affected. Please be careful to download any binary DLL from other web sites, especially we found NuGet packages not owned by us that contain vulnerable versions.\n\n### Workarounds\n\nThere is no workaround available that addresses all issues except updating to latest version from GitHub.\n\n### References\n\nFind original CVE posting here: https://security.snyk.io/vuln/SNYK-DOTNET-AJAXPRO2-1925971\n\nNote: the official Ajax.NET Professional (AjaxPro) NuGet package is available here: https://www.nuget.org/packages/AjaxNetProfessional/\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue on this GitHub repository",
   "severity": [
     {
       "type": "CVSS_V3",
@@ -56,6 +58,10 @@
     {
       "type": "WEB",
       "url": "https://security.snyk.io/vuln/SNYK-DOTNET-AJAXPRO2-1925971"
+    },
+    {
+      "type": "WEB",
+      "url": "http://packetstormsecurity.com/files/175677/AjaxPro-Deserialization-Remote-Code-Execution.html"
     }
   ],
   "database_specific": {

advisories/github-reviewed/2021/12/GHSA-74r6-grj9-8rq6/GHSA-74r6-grj9-8rq6.json

@@ -1,13 +1,12 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-74r6-grj9-8rq6",
-  "modified": "2021-12-06T22:06:15Z",
+  "modified": "2026-02-03T17:39:19Z",
   "published": "2021-12-16T15:27:55Z",
-  "aliases": [
-    "CVE-2021-23758"
-  ],
-  "summary": "Remote Code Execution in AjaxNetProfessional",
-  "details": "All versions of package ajaxpro.2 are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary .NET classes, which can be abused to gain remote code execution.",
+  "withdrawn": "2026-02-03T17:39:19Z",
+  "aliases": [],
+  "summary": "Duplicate Advisory: Remote Code Execution in AjaxNetProfessional",
+  "details": "## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-6r7c-6w96-8pvw. This link is maintained to preserve external references.\n\n## Original Description\nAll versions of package ajaxpro.2 are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary .NET classes, which can be abused to gain remote code execution.",
   "severity": [
     {
       "type": "CVSS_V3",

advisories/github-reviewed/2023/03/GHSA-89p3-9j8c-fqh4/GHSA-89p3-9j8c-fqh4.json

@@ -1,13 +1,12 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-89p3-9j8c-fqh4",
-  "modified": "2025-03-05T19:26:28Z",
+  "modified": "2026-02-03T17:38:51Z",
   "published": "2023-03-12T06:30:21Z",
-  "aliases": [
-    "CVE-2021-46876"
-  ],
-  "summary": "User account enumeration in eZ Publish Ibexa Kernel",
-  "details": "This Security Advisory is about a vulnerability in eZ Platform v1.13, v2.5, and v3.2, and in Ibexa DXP and Ibexa Open Source v3.3. The /user/sessions endpoint can let an attacker detect if a given username or email refers to a valid account. This can be detected through differences in the response data or response time of certain requests. The fix ensures neither attack is possible. The fix is distributed via Composer.",
+  "withdrawn": "2026-02-03T17:38:51Z",
+  "aliases": [],
+  "summary": "Duplicate Advisory: User account enumeration in eZ Publish Ibexa Kernel",
+  "details": "## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-gmrf-99gw-vvwj. This link is maintained to preserve external references.\n\n## Original Description\n\nThis Security Advisory is about a vulnerability in eZ Platform v1.13, v2.5, and v3.2, and in Ibexa DXP and Ibexa Open Source v3.3. The /user/sessions endpoint can let an attacker detect if a given username or email refers to a valid account. This can be detected through differences in the response data or response time of certain requests. The fix ensures neither attack is possible. The fix is distributed via Composer.",
   "severity": [
     {
       "type": "CVSS_V3",

advisories/github-reviewed/2024/04/GHSA-3f95-mxq2-2f63/GHSA-3f95-mxq2-2f63.json

@@ -1,13 +1,12 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-3f95-mxq2-2f63",
-  "modified": "2024-04-10T22:12:50Z",
+  "modified": "2026-02-03T17:39:05Z",
   "published": "2024-04-10T18:30:48Z",
-  "aliases": [
-    "CVE-2024-1728"
-  ],
-  "summary": "Gradio Local File Inclusion vulnerability",
-  "details": "gradio-app/gradio is vulnerable to a local file inclusion vulnerability due to improper validation of user-supplied input in the UploadButton component. Attackers can exploit this vulnerability to read arbitrary files on the filesystem, such as private SSH keys, by manipulating the file path in the request to the `/queue/join` endpoint. This issue could potentially lead to remote code execution. The vulnerability is present in the handling of file upload paths, allowing attackers to redirect file uploads to unintended locations on the server.",
+  "withdrawn": "2026-02-03T17:39:05Z",
+  "aliases": [],
+  "summary": "Duplicate Advisory: Gradio Local File Inclusion vulnerability",
+  "details": "## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-m842-4qm8-7gpq. This link is maintained to preserve external references.\n\n## Original Description\ngradio-app/gradio is vulnerable to a local file inclusion vulnerability due to improper validation of user-supplied input in the UploadButton component. Attackers can exploit this vulnerability to read arbitrary files on the filesystem, such as private SSH keys, by manipulating the file path in the request to the `/queue/join` endpoint. This issue could potentially lead to remote code execution. The vulnerability is present in the handling of file upload paths, allowing attackers to redirect file uploads to unintended locations on the server.",
   "severity": [
     {
       "type": "CVSS_V3",

advisories/github-reviewed/2024/09/GHSA-m842-4qm8-7gpq/GHSA-m842-4qm8-7gpq.json

@@ -1,9 +1,11 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-m842-4qm8-7gpq",
-  "modified": "2024-09-25T21:48:24Z",
+  "modified": "2026-02-03T17:39:09Z",
   "published": "2024-09-25T21:48:24Z",
-  "aliases": [],
+  "aliases": [
+    "CVE-2024-1728"
+  ],
   "summary": "Gradio allows users to access arbitrary files",
   "details": "### Impact\nThis vulnerability allows users of Gradio applications that have a public link (such as on Hugging Face Spaces) to access files on the machine hosting the Gradio application. This involves intercepting and modifying the network requests made by the Gradio app to the server. \n\n### Patches\nYes, the problem has been patched in Gradio version 4.19.2 or higher. We have no knowledge of this exploit being used against users of Gradio applications, but we encourage all users to upgrade to Gradio 4.19.2 or higher.\n\nFixed in: https://github.com/gradio-app/gradio/commit/16fbe9cd0cffa9f2a824a0165beb43446114eec7\nCVE: https://nvd.nist.gov/vuln/detail/CVE-2024-1728",
   "severity": [
@@ -42,17 +44,27 @@
       "type": "WEB",
       "url": "https://github.com/gradio-app/gradio/security/advisories/GHSA-m842-4qm8-7gpq"
     },
+    {
+      "type": "ADVISORY",
+      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-1728"
+    },
     {
       "type": "WEB",
       "url": "https://github.com/gradio-app/gradio/commit/16fbe9cd0cffa9f2a824a0165beb43446114eec7"
     },
     {
       "type": "PACKAGE",
       "url": "https://github.com/gradio-app/gradio"
+    },
+    {
+      "type": "WEB",
+      "url": "https://huntr.com/bounties/9bb33b71-7995-425d-91cc-2c2a2f2a068a"
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
+    "cwe_ids": [
+      "CWE-22"
+    ],
     "severity": "CRITICAL",
     "github_reviewed": true,
     "github_reviewed_at": "2024-09-25T21:48:24Z",