7.5
CVE-2022-23308
- EPSS 0.06%
- Veröffentlicht 26.02.2022 05:15:08
- Zuletzt bearbeitet 05.05.2025 17:17:56
- Quelle cve@mitre.org
- Teams Watchlist Login
- Unerledigt Login
valid.c in libxml2 before 2.9.13 has a use-after-free of ID and IDREF attributes.
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Fedoraproject ≫ Fedora Version34
Debian ≫ Debian Linux Version9.0
Netapp ≫ Active Iq Unified Manager Version- SwPlatformvmware_vsphere
Netapp ≫ Clustered Data Ontap Version-
Netapp ≫ Clustered Data Ontap Antivirus Connector Version-
Netapp ≫ Manageability Software Development Kit Version-
Netapp ≫ Ontap Select Deploy Administration Utility Version-
Netapp ≫ Smi-s Provider Version-
Netapp ≫ Snapmanager Version- SwPlatformoracle
Netapp ≫ Bootstrap Os Version-
Netapp ≫ H300s Firmware Version-
Netapp ≫ H500s Firmware Version-
Netapp ≫ H700s Firmware Version-
Netapp ≫ H300e Firmware Version-
Netapp ≫ H500e Firmware Version-
Netapp ≫ H700e Firmware Version-
Netapp ≫ H410s Firmware Version-
Netapp ≫ H410c Firmware Version-
Oracle ≫ Communications Cloud Native Core Binding Support Function Version22.2.0
Oracle ≫ Communications Cloud Native Core Network Repository Function Version22.1.2
Oracle ≫ Communications Cloud Native Core Network Repository Function Version22.2.0
Oracle ≫ Communications Cloud Native Core Unified Data Repository Version22.2.0
Oracle ≫ Mysql Workbench Version <= 8.0.29
Oracle ≫ Zfs Storage Appliance Kit Version8.8
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
Typ | Quelle | Score | Percentile |
---|---|---|---|
EPSS | FIRST.org | 0.06% | 0.172 |
Quelle | Base Score | Exploit Score | Impact Score | Vector String |
---|---|---|---|---|
nvd@nist.gov | 7.5 | 3.9 | 3.6 |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
|
nvd@nist.gov | 4.3 | 8.6 | 2.9 |
AV:N/AC:M/Au:N/C:N/I:N/A:P
|
134c704f-9b21-4f2e-91b3-4a467353bcc0 | 7.5 | 3.9 | 3.6 |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
|
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.