This page was not yet optimized for use on mobile devices.
CVE-2025-30472
Data ?
Vulnerability ID | CVE-2025-30472 |
---|---|
Published on | 22.03.2025 02:15 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:corosync:corosync:0.00:*:*:*:*:*:*:*,
cpe:2.3:a:corosync:corosync:0.90:*:*:*:*:*:*:*,
cpe:2.3:a:corosync:corosync:0.91:*:*:*:*:*:*:*,
cpe:2.3:a:corosync:corosync:0.92:*:*:*:*:*:*:*,
cpe:2.3:a:corosync:corosync:0.93:*:*:*:*:*:*:*,
cpe:2.3:a:corosync:corosync:0.94:*:*:*:*:*:*:*,
cpe:2.3:a:corosync:corosync:0.95:*:*:*:*:*:*:*,
cpe:2.3:a:corosync:corosync:0.96:*:*:*:*:*:*:*,
cpe:2.3:a:corosync:corosync:0.97:*:*:*:*:*:*:*,
cpe:2.3:a:corosync:corosync:0.98:*:*:*:*:*:*:*,
…
Vulnerable certificates ?
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.