Mar 4, 2026, 3:45 PM |
Mar 3, 2026, 11:48 AM - CVE (set "CVE" coverage to "CVE-2024-41080,CVE-2024-50036,CVE-2024-50264,CVE-2024-50265,CVE-2024-50267,CVE-2024-50268,CVE-2024-50269,CVE-2024-50273,CVE-2024-50278,CVE-2024-50279,CVE-2024-50282,CVE-2024-50287,CVE-2024-50290,CVE-2024-50292,CVE-2024-50295,CVE-2024-50296,CVE-2024-50299,CVE-2024-50301,CVE-2024-50302,CVE-2024-53052,CVE-2024-53060,CVE-2024-53061,CVE-2024-53063,CVE-2024-53066,CVE-2024-53101,CVE-2024-53103,CVE-2024-53104")
- CVSSv2 score source (changed from "CVE-2024-53103" to "CVE-2024-53104")
|
Mar 5, 2025, 8:29 AM - CISA reference
- CVSS temporal metrics ("CVSSv2 temporal vector" set to "CVSS2#E:F/RL:OF/RC:C")
- CVSS temporal metrics ("CVSSv3 temporal vector" set to "CVSS:3.0/E:F/RL:O/RC:C")
- Exploit attributes ("Exploit available" set to "True")
- Exploit attributes ("Exploitability ease" changed from "No known exploits are available" to "Exploits are available")
|
Jan 9, 2025, 10:03 AM - CVE (set "CVE" coverage to "CVE-2024-50036,CVE-2024-50264,CVE-2024-50273,CVE-2024-50282,CVE-2024-50299,CVE-2024-50301,CVE-2024-50302,CVE-2024-53060,CVE-2024-53066,CVE-2024-53103")
- CVSS metrics ("Cvssv4 score" set to 0.0)
- CVSSv2 score source (changed from "CVE-2024-50264" to "CVE-2024-53103")
- CVSSv2 severity (based on None, severity decreased from "High" to "Low")
|
Jan 8, 2025, 10:03 AM - CVE (set "CVE" coverage to "CVE-2024-50036,CVE-2024-50264,CVE-2024-50282,CVE-2024-50301,CVE-2024-53060,CVE-2024-53066")
- CVSS metrics ("Cvssv4 score" set to 0.0)
- CVSSv2 severity (based on None, severity decreased from "High" to "Low")
|
Jan 1, 2025, 10:07 AM |