| May 17, 2024, 5:22 PM | 
| Jan 3, 2024, 4:28 PM | 
| May 19, 2023, 7:58 AM | 
| May 14, 2023, 10:07 AM CVSS metrics ("CVSSv2 score" changed from 2.1 to 4.0. "CVSSv2 vector" changed from "CVSS2#AV:N/AC:H/Au:S/C:P/I:N/A:N" to "CVSS2#AV:N/AC:L/Au:S/C:P/I:N/A:N". "CVSSv3 score" changed from 3.1 to 4.3. "CVSSv3 vector" changed from "CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N" to "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N")CVSSv2 severity (based on CVE-2022-4376, severity increased from "Low" to "Medium")CVSSv3 score source (set to "CVE-2022-4376")CVSSv3 severity (based on CVE-2022-4376, severity increased from "Low" to "Medium")
 | 
| May 14, 2023, 6:02 AM CVSSv2 severity (based on CVE-2022-4376, severity increased from "Low" to "Medium")CVSSv3 severity (based on CVE-2022-4376, severity increased from "Low" to "Medium")CVSS metrics ("CVSSv2 score" changed from 2.1 to 4.0. "CVSSv2 vector" changed from "CVSS2#AV:N/AC:H/Au:S/C:P/I:N/A:N" to "CVSS2#AV:N/AC:L/Au:S/C:P/I:N/A:N". "CVSSv3 score" changed from 3.1 to 4.3. "CVSSv3 vector" changed from "CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N" to "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N")CVSSv3 score source (set to "CVE-2022-4376")
 | 
| May 14, 2023, 2:08 AM CVSS metrics ("CVSSv2 score" changed from 2.1 to 4.0. "CVSSv2 vector" changed from "CVSS2#AV:N/AC:H/Au:S/C:P/I:N/A:N" to "CVSS2#AV:N/AC:L/Au:S/C:P/I:N/A:N". "CVSSv3 score" changed from 3.1 to 4.3. "CVSSv3 vector" changed from "CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N" to "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N")CVSSv2 severity (based on CVE-2022-4376, severity increased from "Low" to "Medium")CVSSv3 score source (set to "CVE-2022-4376")CVSSv3 severity (based on CVE-2022-4376, severity increased from "Low" to "Medium")
 | 
| May 4, 2023, 10:05 PM | 
| May 2, 2023, 5:57 PM | 
* Changelogs are generally available for changes made after Nov 1, 2022