This page was not yet optimized for use on mobile devices.
CVE-2023-39616
Data ?
Vulnerability ID | CVE-2023-39616 |
---|---|
Published on | 29.08.2023 17:15 |
Severity | HIGH |
Vulnerable configurations ?
- cpe:2.3:a:aomedia:aomedia:3.0.0:*:*:*:*:*:*:*, cpe:2.3:a:aomedia:aomedia:3.1.0:*:*:*:*:*:*:*, cpe:2.3:a:aomedia:aomedia:3.1.1:*:*:*:*:*:*:*, cpe:2.3:a:aomedia:aomedia:3.1.2:*:*:*:*:*:*:*, cpe:2.3:a:aomedia:aomedia:3.1.3:*:*:*:*:*:*:*, cpe:2.3:a:aomedia:aomedia:3.2.0:*:*:*:*:*:*:*, cpe:2.3:a:aomedia:aomedia:3.3.0:*:*:*:*:*:*:*, cpe:2.3:a:aomedia:aomedia:3.4.0:*:*:*:*:*:*:*, cpe:2.3:a:aomedia:aomedia:3.5.0:*:*:*:*:*:*:*
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.