Publish Advisories

GHSA-6749-m5cp-6cg7 GHSA-f3f8-vx3w-hp5q GHSA-f8c8-4pm7-w885
2026-05-22 18:04:22 -07:00 · 2025-04-08 17:55:27 +00:00
parent 9bf96dd361
commit 52cb2e421d
3 changed files with 18 additions and 6 deletions
@@ -1,13 +1,13 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-6749-m5cp-6cg7",
-  "modified": "2025-01-22T17:33:34Z",
+  "modified": "2025-04-08T17:53:18Z",
  "published": "2024-02-24T00:30:20Z",
  "aliases": [
    "CVE-2024-27132"
  ],
  "summary": "Cross-site Scripting in MLFlow",
-  "details": "Insufficient sanitization in MLflow leads to XSS when running an untrusted recipe.\n\nThis issue leads to a client-side RCE when running an untrusted recipe in Jupyter Notebook.\n\nThe vulnerability stems from lack of sanitization over template variables.\n\n",
+  "details": "Insufficient sanitization in MLflow leads to XSS when running an untrusted recipe.\n\nThis issue leads to a client-side RCE when running an untrusted recipe in Jupyter Notebook.\n\nThe vulnerability stems from lack of sanitization over template variables.",
  "severity": [
    {
      "type": "CVSS_V3",
@@ -48,6 +48,10 @@
      "type": "PACKAGE",
      "url": "https://github.com/mlflow/mlflow"
    },
+    {
+      "type": "WEB",
+      "url": "https://github.com/pypa/advisory-database/tree/main/vulns/mlflow/PYSEC-2024-240.yaml"
+    },
    {
      "type": "WEB",
      "url": "https://research.jfrog.com/vulnerabilities/mlflow-untrusted-recipe-xss-jfsa-2024-000631930"
@@ -1,13 +1,13 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-f3f8-vx3w-hp5q",
-  "modified": "2024-11-06T15:57:08Z",
+  "modified": "2025-04-08T17:52:08Z",
  "published": "2024-11-06T15:57:08Z",
  "aliases": [
    "CVE-2024-10081"
  ],
  "summary": "codechecker vulnerable to authentication bypass when using specifically crafted URLs",
-  "details": "### Summary\nAuthentication bypass occurs when the API URL ends with Authentication, Configuration or ServerInfo. This bypass allows superuser access to all API endpoints other than Authentication. These endpoints include the ability to add, edit, and remove products, among others.\n\n### Details\nAll endpoints, apart from the /Authentication is affected by the vulnerability.\n\nThe vulnerability allows unauthenticated users to access all API functionality.\nYou can look for the following pattern in the logs to check if the vulnerabilty was exploited:\n![image](https://github.com/user-attachments/assets/6ba02231-a3d8-4832-aee6-f96462b7441e)\n\nNote that the url starts with v and contains a valid CodeChecker endpoint, but it ends in `Authentication`, `Configuration` or `ServerInfo` and it was made by an `Anonymous` user.\n\n### Impact\nThis authentication bypass allows querying, adding, changing, and deleting Products contained on the CodeChecker server, without authentication, by an anonymous user.\n",
+  "details": "### Summary\nAuthentication bypass occurs when the API URL ends with Authentication, Configuration or ServerInfo. This bypass allows superuser access to all API endpoints other than Authentication. These endpoints include the ability to add, edit, and remove products, among others.\n\n### Details\nAll endpoints, apart from the /Authentication is affected by the vulnerability.\n\nThe vulnerability allows unauthenticated users to access all API functionality.\nYou can look for the following pattern in the logs to check if the vulnerabilty was exploited:\n![image](https://github.com/user-attachments/assets/6ba02231-a3d8-4832-aee6-f96462b7441e)\n\nNote that the url starts with v and contains a valid CodeChecker endpoint, but it ends in `Authentication`, `Configuration` or `ServerInfo` and it was made by an `Anonymous` user.\n\n### Impact\nThis authentication bypass allows querying, adding, changing, and deleting Products contained on the CodeChecker server, without authentication, by an anonymous user.",
  "severity": [
    {
      "type": "CVSS_V3",
@@ -58,6 +58,10 @@
    {
      "type": "PACKAGE",
      "url": "https://github.com/Ericsson/codechecker"
+    },
+    {
+      "type": "WEB",
+      "url": "https://github.com/pypa/advisory-database/tree/main/vulns/codechecker/PYSEC-2024-238.yaml"
    }
  ],
  "database_specific": {
@@ -1,13 +1,13 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-f8c8-4pm7-w885",
-  "modified": "2025-01-21T20:25:05Z",
+  "modified": "2025-04-08T17:52:35Z",
  "published": "2025-01-21T20:25:05Z",
  "aliases": [
    "CVE-2024-53829"
  ],
  "summary": "Cross-Site Request Forgery in CodeChecker API",
-  "details": "### Summary\nCross-site request forgery allows an unauthenticated attacker to hijack the authentication of a logged in user, and use the web API with the same permissions.\n\n### Details\nSecurity attributes like HttpOnly and SameSite are missing from the session cookie, allowing its use from XHR requests and form submissions.\nThe CodeChecker API endpoints only require the session cookie, they do not require a CSRF token, and missing HTTP headers allow the form submission to succeed (but not XHR). This means that the attacker needs to know the ID of products to edit or delete them, but it does not need knowledge to create new products with the SQLite backend.\n\n### PoC\nWith a superuser logged into CodeChecker.\n\n```html\n<html><body>\n    <form action=\"https://codechecker.example.com/v6.58/Products\" method=\"POST\" enctype=\"text/plain\">\n        <input type=\"text\" name='[1,\"getProducts\",1,1,{}]' value=''>\n    </form>\n    <script>document.forms[0].submit()</script>\n</body></html>\n```\nOr the same form attack on any of the applicable endpoints.\n\n### Impact\nThe vulnerability allows an attacker to make requests to CodeChecker as the currently logged in user, including but not limited to adding, removing or editing products. The attacker needs to know the ID of the available products to modify or delete them. The attacker cannot directly exfiltrate data from CodeChecker, due to being limited to form-based CSRF.\n",
+  "details": "### Summary\nCross-site request forgery allows an unauthenticated attacker to hijack the authentication of a logged in user, and use the web API with the same permissions.\n\n### Details\nSecurity attributes like HttpOnly and SameSite are missing from the session cookie, allowing its use from XHR requests and form submissions.\nThe CodeChecker API endpoints only require the session cookie, they do not require a CSRF token, and missing HTTP headers allow the form submission to succeed (but not XHR). This means that the attacker needs to know the ID of products to edit or delete them, but it does not need knowledge to create new products with the SQLite backend.\n\n### PoC\nWith a superuser logged into CodeChecker.\n\n```html\n<html><body>\n    <form action=\"https://codechecker.example.com/v6.58/Products\" method=\"POST\" enctype=\"text/plain\">\n        <input type=\"text\" name='[1,\"getProducts\",1,1,{}]' value=''>\n    </form>\n    <script>document.forms[0].submit()</script>\n</body></html>\n```\nOr the same form attack on any of the applicable endpoints.\n\n### Impact\nThe vulnerability allows an attacker to make requests to CodeChecker as the currently logged in user, including but not limited to adding, removing or editing products. The attacker needs to know the ID of the available products to modify or delete them. The attacker cannot directly exfiltrate data from CodeChecker, due to being limited to form-based CSRF.",
  "severity": [
    {
      "type": "CVSS_V3",
@@ -47,6 +47,10 @@
    {
      "type": "PACKAGE",
      "url": "https://github.com/Ericsson/codechecker"
+    },
+    {
+      "type": "WEB",
+      "url": "https://github.com/pypa/advisory-database/tree/main/vulns/codechecker/PYSEC-2025-12.yaml"
    }
  ],
  "database_specific": {