diff --git a/advisories/github-reviewed/2023/12/GHSA-f23h-52hj-99p6/GHSA-f23h-52hj-99p6.json b/advisories/github-reviewed/2023/12/GHSA-f23h-52hj-99p6/GHSA-f23h-52hj-99p6.json index 3a49615844a..05e9e22db78 100644 --- a/advisories/github-reviewed/2023/12/GHSA-f23h-52hj-99p6/GHSA-f23h-52hj-99p6.json +++ b/advisories/github-reviewed/2023/12/GHSA-f23h-52hj-99p6/GHSA-f23h-52hj-99p6.json @@ -1,14 +1,19 @@ { "schema_version": "1.4.0", "id": "GHSA-f23h-52hj-99p6", - "modified": "2023-12-21T18:10:56Z", + "modified": "2025-02-13T19:30:31Z", "published": "2023-12-21T12:30:29Z", "aliases": [ "CVE-2023-51656" ], "summary": "Apache IoTDB: Unsafe deserialize map in Sync Tool", - "details": "Deserialization of Untrusted Data vulnerability in Apache IoTDB.This issue affects Apache IoTDB: from 0.13.0 through 0.13.4.\n\nUsers are recommended to upgrade to version 1.2.2, which fixes the issue.\n\n", - "severity": [], + "details": "Deserialization of Untrusted Data vulnerability in Apache IoTDB.This issue affects Apache IoTDB: from 0.13.0 through 0.13.4.\n\nUsers are recommended to upgrade to version 1.2.2, which fixes the issue.", + "severity": [ + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H" + } + ], "affected": [ { "package": { @@ -52,7 +57,7 @@ "cwe_ids": [ "CWE-502" ], - "severity": "HIGH", + "severity": "CRITICAL", "github_reviewed": true, "github_reviewed_at": "2023-12-21T18:10:56Z", "nvd_published_at": "2023-12-21T12:15:08Z" diff --git a/advisories/github-reviewed/2024/01/GHSA-h5c8-rqwp-cp95/GHSA-h5c8-rqwp-cp95.json b/advisories/github-reviewed/2024/01/GHSA-h5c8-rqwp-cp95/GHSA-h5c8-rqwp-cp95.json index 7f8f3aaae1d..ab0b698b593 100644 --- a/advisories/github-reviewed/2024/01/GHSA-h5c8-rqwp-cp95/GHSA-h5c8-rqwp-cp95.json +++ b/advisories/github-reviewed/2024/01/GHSA-h5c8-rqwp-cp95/GHSA-h5c8-rqwp-cp95.json @@ -1,7 +1,7 @@ { "schema_version": "1.4.0", "id": "GHSA-h5c8-rqwp-cp95", - "modified": "2024-01-11T15:20:48Z", + "modified": "2025-02-13T19:31:33Z", "published": "2024-01-11T15:20:48Z", "aliases": [ "CVE-2024-22195" diff --git a/advisories/github-reviewed/2024/01/GHSA-rxgg-273w-rfw7/GHSA-rxgg-273w-rfw7.json b/advisories/github-reviewed/2024/01/GHSA-rxgg-273w-rfw7/GHSA-rxgg-273w-rfw7.json index 3249c6fe3ca..dfa16efaddc 100644 --- a/advisories/github-reviewed/2024/01/GHSA-rxgg-273w-rfw7/GHSA-rxgg-273w-rfw7.json +++ b/advisories/github-reviewed/2024/01/GHSA-rxgg-273w-rfw7/GHSA-rxgg-273w-rfw7.json @@ -1,13 +1,13 @@ { "schema_version": "1.4.0", "id": "GHSA-rxgg-273w-rfw7", - "modified": "2024-09-12T21:02:56Z", + "modified": "2025-02-13T19:31:37Z", "published": "2024-01-15T12:30:19Z", "aliases": [ "CVE-2023-46226" ], "summary": "Remote Code Execution vulnerability in Apache IoTDB via UDF", - "details": "Remote Code Execution vulnerability in Apache IoTDB. This issue affects Apache IoTDB from 1.0.0 through 1.2.2.\n\nUsers are recommended to upgrade to version 1.3.0, which fixes the issue.\n\n", + "details": "Remote Code Execution vulnerability in Apache IoTDB. This issue affects Apache IoTDB from 1.0.0 through 1.2.2.\n\nUsers are recommended to upgrade to version 1.3.0, which fixes the issue.", "severity": [ { "type": "CVSS_V3", diff --git a/advisories/github-reviewed/2024/02/GHSA-h2rq-qhr7-53gm/GHSA-h2rq-qhr7-53gm.json b/advisories/github-reviewed/2024/02/GHSA-h2rq-qhr7-53gm/GHSA-h2rq-qhr7-53gm.json index 5efa82d4467..9aa31a99823 100644 --- a/advisories/github-reviewed/2024/02/GHSA-h2rq-qhr7-53gm/GHSA-h2rq-qhr7-53gm.json +++ b/advisories/github-reviewed/2024/02/GHSA-h2rq-qhr7-53gm/GHSA-h2rq-qhr7-53gm.json @@ -1,13 +1,13 @@ { "schema_version": "1.4.0", "id": "GHSA-h2rq-qhr7-53gm", - "modified": "2024-02-14T14:52:14Z", + "modified": "2025-02-13T19:31:02Z", "published": "2024-02-06T12:30:30Z", "aliases": [ "CVE-2024-23673" ], "summary": "Apache Sling Servlets Resolver executes malicious code via path traversal", - "details": "\nMalicious code execution via path traversal in Apache Software Foundation Apache Sling Servlets Resolver.This issue affects all version of Apache Sling Servlets Resolver before 2.11.0. However, whether a system is vulnerable to this attack depends on the exact configuration of the system.\nIf the system is vulnerable, a user with write access to the repository might be able to trick the Sling Servlet Resolver to load a previously uploaded script. \n\nUsers are recommended to upgrade to version 2.11.0, which fixes this issue. It is recommended to upgrade, regardless of whether your system configuration currently allows this attack or not.", + "details": "Malicious code execution via path traversal in Apache Software Foundation Apache Sling Servlets Resolver.This issue affects all version of Apache Sling Servlets Resolver before 2.11.0. However, whether a system is vulnerable to this attack depends on the exact configuration of the system.\nIf the system is vulnerable, a user with write access to the repository might be able to trick the Sling Servlet Resolver to load a previously uploaded script. \n\nUsers are recommended to upgrade to version 2.11.0, which fixes this issue. It is recommended to upgrade, regardless of whether your system configuration currently allows this attack or not.", "severity": [ { "type": "CVSS_V3",