LiveActive security incident?Get immediate response
CVE Record

CVE-2023-34473: Usage of Hard-coded Credentials

AMI SPx contains a vulnerability in the BMC where a valid user may cause a use of hard-coded credentials. A successful exploit of this vulnerability may lead to a loss of confidentiality, integrity, and availability.

MediumCVSS 6.6Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-34473 is a hard-coded credentials issue in AMI MegaRAC_SPx 12.0 BMC software. The sources indicate a valid high-privileged user and user interaction are required, but successful exploitation could affect confidentiality, integrity, and availability.

Executive priority

Treat this as a moderate-priority infrastructure firmware issue. It is not reported as exploited in the provided sources, but BMC compromise can carry high operational impact, so exposure mapping and vendor firmware review should not wait.

Technical view

The CVE describes CWE-798 in the AMI SPx BMC, where a valid user may trigger use of hard-coded credentials. CVSS 3.1 is 6.6 with adjacent attack vector, low complexity, high privileges, required user interaction, unchanged scope, and high C/I/A impact.

Likely exposure

Exposure is limited to environments running AMI MegaRAC_SPx 12.0 in BMC firmware. The bundle does not identify downstream OEM products, so teams must map server platforms to AMI SPx use through asset inventory and vendor guidance.

Exploitation context

CISA KEV is false in the provided bundle, and no cited source states active exploitation. The CVSS vector indicates exploitation is not remote internet-scale by default: it requires adjacent access, high privileges, and user interaction.

Researcher notes

Evidence is sparse beyond the CVE metadata and AMI advisory reference. Do not assume affected OEM platforms, fixed versions, exploit availability, or concrete remediation details unless confirmed by AMI or the relevant hardware vendor.

Mitigation direction

  • Check AMI and hardware vendor advisories for firmware guidance.
  • Inventory BMCs and identify AMI MegaRAC_SPx 12.0 deployments.
  • Restrict BMC access to trusted management networks only.
  • Review and reduce high-privilege BMC accounts.
  • Monitor BMC logs for unusual privileged user activity.

Validation and detection

  • Confirm BMC firmware product and version against asset records.
  • Map affected AMI SPx use through server vendor documentation.
  • Verify BMC management interfaces are not broadly reachable.
  • Review privileged BMC account lists and recent activity.
  • Track AMI advisory updates for named fixes or mitigations.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-798: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-34473 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.6CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H0.75.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.6Medium
CVSS 3.1 vector shape for CVE-2023-34473Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AMIMegaRAC_SPx12.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-798 · source CWE mapping

Use of Hard-coded Credentials

Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.