From f572ba225daba4dde9ca81f5ac8032922a74d75f Mon Sep 17 00:00:00 2001
From: "advisory-database[bot]"
 <45398580+advisory-database[bot]@users.noreply.github.com>
Date: Fri, 21 Mar 2025 14:16:05 +0000
Subject: [PATCH] Publish GHSA-4h8f-2wvx-gg5w

---
 .../GHSA-4h8f-2wvx-gg5w/GHSA-4h8f-2wvx-gg5w.json  | 15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)

diff --git a/advisories/github-reviewed/2024/05/GHSA-4h8f-2wvx-gg5w/GHSA-4h8f-2wvx-gg5w.json b/advisories/github-reviewed/2024/05/GHSA-4h8f-2wvx-gg5w/GHSA-4h8f-2wvx-gg5w.json
index 7ebe9b62a69..246e690601e 100644
--- a/advisories/github-reviewed/2024/05/GHSA-4h8f-2wvx-gg5w/GHSA-4h8f-2wvx-gg5w.json
+++ b/advisories/github-reviewed/2024/05/GHSA-4h8f-2wvx-gg5w/GHSA-4h8f-2wvx-gg5w.json
@@ -1,14 +1,19 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-4h8f-2wvx-gg5w",
-  "modified": "2025-01-17T16:27:53Z",
+  "modified": "2025-03-21T14:14:22Z",
   "published": "2024-05-03T18:30:37Z",
   "aliases": [
     "CVE-2024-34447"
   ],
   "summary": "Bouncy Castle Java Cryptography API vulnerable to DNS poisoning",
   "details": "An issue was discovered in Bouncy Castle Java Cryptography APIs before BC 1.78. When endpoint identification is enabled in the BCJSSE and an SSL socket is created without an explicit hostname (as happens with HttpsURLConnection), hostname verification could be performed against a DNS-resolved IP address in some situations, opening up a possibility of DNS poisoning.",
-  "severity": [],
+  "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N"
+    }
+  ],
   "affected": [
     {
       "package": {
@@ -114,8 +119,10 @@
     }
   ],
   "database_specific": {
-    "cwe_ids": [],
-    "severity": "LOW",
+    "cwe_ids": [
+      "CWE-297"
+    ],
+    "severity": "MODERATE",
     "github_reviewed": true,
     "github_reviewed_at": "2024-05-03T20:34:32Z",
     "nvd_published_at": "2024-05-03T16:15:11Z"