Intel Data Center Manager 5.0.2

CPE Details

Intel Data Center Manager 5.0.2
intel
data_center_manager
5.0.2
2019-03-19
13h32 +00:00
2019-03-19
13h32 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:intel:data_center_manager:5.0.2:*:*:*:*:*:*:*

Informations

Vendor

intel

Product

data_center_manager

Version

5.0.2

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2023-31273 2023-11-14 19h04 +00:00 Protection mechanism failure in some Intel DCM software before version 5.2 may allow an unauthenticated user to potentially enable escalation of privilege via network access.
10
Critical
CVE-2022-44610 2023-05-10 13h17 +00:00 Improper authentication in the Intel(R) DCM software before version 5.1 may allow an authenticated user to potentially enable escalation of privilege via network access.
8.8
High
CVE-2022-41979 2023-05-10 13h17 +00:00 Protection mechanism failure in the Intel(R) DCM software before version 5.1 may allow an authenticated user to potentially enable escalation of privilege via network access.
8.8
High
CVE-2022-43475 2023-05-10 13h17 +00:00 Insecure storage of sensitive information in the Intel(R) DCM software before version 5.1 may allow an authenticated user to potentially enable escalation of privilege via local access.
7.8
High
CVE-2022-41998 2023-05-10 13h17 +00:00 Uncontrolled search path in the Intel(R) DCM software before version 5.1 may allow an authenticated user to potentially enable escalation of privilege via local access.
7.8
High
CVE-2022-44619 2023-05-10 13h17 +00:00 Insecure storage of sensitive information in the Intel(R) DCM software before version 5.1 may allow an authenticated user to potentially enable escalation of privilege via local access.
8.2
High
CVE-2021-44228 2021-12-10 00h00 +00:00 Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.
10
Critical