Hdm Family A G5
Approved changes feed: RSS · Atom
cpe:2.3:a:h3c:hdm_family-a_g5:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | H3C (17378f50-e353-55bc-ad2a-c62425dcc44c) |
|---|---|
| Product | Hdm Family A G5 (5da412bd-be5a-51d6-af79-82dc4d5104e4) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-65197 |
vulnerable | 2026-11-03 10:16:20.841663 |
H3C G3/G5 HDM Firmware Verification Key Replacement
LOW (3.1)
H3C HDM Family-A verifies the RSA signature of a firmware image against a public key it reads from the mutable file `/conf/public.pem`. That file is writable by an authenticated Redfish client through the `UpdateService.UploadSignKey` action, which stores the uploaded body verbatim after validating only that the multipart filename ends in `.pem`. An administrator, or any account with `firmware-update` privilege, can therefore replace the trust anchor with their own key, sign a malicious image with the matching private key, and have it pass verification. Family-A has no hardware root-of-trust (no PFR) to catch the substituted key.
This was observed on H3C HDM Family-A G5 HDM 6.14.01. H3C HDM Family-A G3/G5 builds carrying the Redfish/DRE update tree appear to be affected. HDM2 uses a different update path and is not covered by this finding.
Published: 2026-10-13T14:17:54.265Z
Updated: 2026-10-14T18:59:13.586Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.