Insufficient key management for Intel(R) Data Center Manager SDK before version 5.0.2 may…
Priority LOW 25Published · Updated
Key facts
- Attack vector
- Local
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- No fix listed
Attack profile from CVSS 3.0 · NVD. Fix status from CNA.
Summary
Insufficient key management for Intel(R) Data Center Manager SDK before version 5.0.2 may allow an authenticated user to potentially enable information disclosure via local access.
Why it matters now
EPSS 0.00455 39th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | — | all versions | — | No fix listed | CNA |
- — Vendor— Affected all versions Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2019-0110
- 2026-10-03 Alias added: GHSA-2fj2-4833-36ww
References
More Intel Data Center Manager vulnerabilities
- TI-2022-05617 Improper neutralization in the Intel(R) Data Center Manager software before version 4.1… CVSS 3.1HIGH 8.0
- TI-2023-14957 Protection mechanism failure in Intel DCM software CVSS 3.1CRITICAL 10.0
- TI-2018-02688 Escalation of privilege in Reference UI in Intel Data Center Manager SDK 5.0 and before… CVSS 3.0CRITICAL 9.6
- TI-2022-14945 Protection mechanism failure in Intel DCM software CVSS 3.1HIGH 8.8
- TI-2020-09871 Improper input validation in Intel Data Center Manager Console CVSS 3.1HIGH 8.8
- TI-2019-00087 Insufficient session authentication in web server for Intel(R) Data Center Manager SDK… CVSS 3.0HIGH 8.8
Sources
- CVE-2019-0110 · CVE Program
- CVE-2019-0110 · NVD
- FIRST EPSS
- GHSA-2fj2-4833-36ww · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences