LiveActive security incident?Get immediate response
CVE Record

CVE-2023-34337: Inadequate Encryption Strength

AMI SPx contains a vulnerability in the BMC where a user may cause an inadequate encryption strength by hash-based message authentication code (HMAC). A successful exploit of this vulnerability may lead to a loss of confidentiality, integrity, and availability.

HighCVSS 7.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This affects AMI MegaRAC SPx 12.0 BMC firmware. The issue weakens HMAC-based protection, which can undermine trust in BMC communications or data. A successful exploit may affect confidentiality, integrity, and availability. The provided data rates it high, but exploitation requires adjacent network access, low privileges, high complexity, and user interaction.

Executive priority

Treat as a high-priority infrastructure firmware issue for environments with AMI-based BMCs. Prioritize inventory and vendor confirmation first, then patch or isolate affected management interfaces based on AMI/OEM guidance.

Technical view

CVE-2023-34337 is CWE-326 inadequate encryption strength in AMI SPx BMC HMAC handling. The CVSS 3.1 vector is AV:A/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H, indicating adjacent attack path, high complexity, low privileges, user interaction, changed scope, and high CIA impact.

Likely exposure

Exposure is likely limited to systems or appliances using AMI MegaRAC_SPx version 12.0 BMC firmware. The bundle marks other versions as unaffected by default, but OEM firmware packaging may require asset-level confirmation.

Exploitation context

The bundle does not indicate active exploitation, and KEV is false. The CVSS vector suggests exploitation is not internet-wide by default; it requires adjacent access, low privileges, user interaction, and high attack complexity.

Researcher notes

Evidence is limited to the CVE metadata and AMI advisory reference. The public bundle does not provide exploit details, proof-of-concept status, or named fixed versions. Avoid assuming affected OEM products without mapping their BMC firmware to AMI MegaRAC_SPx 12.0.

Mitigation direction

  • Identify BMC assets running AMI MegaRAC_SPx 12.0.
  • Check AMI and OEM firmware advisories for patches or approved remediation.
  • Restrict BMC management access to trusted administrative networks.
  • Review BMC account privileges and remove unnecessary users.
  • Monitor BMC management networks for unusual authenticated activity.

Validation and detection

  • Inventory server BMC firmware versions and map OEM builds to AMI MegaRAC_SPx.
  • Confirm whether any asset runs MegaRAC_SPx 12.0.
  • Review AMI-SA-2023006 and OEM advisories for fixed versions.
  • Verify BMC interfaces are not reachable from untrusted adjacent networks.
  • Document compensating controls where patch status is unknown.
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 · low confidence lookup

CWE-326: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-34337 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
High
CVSS
7.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:C/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
7.6CVSS 3.1HighCVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H0.96Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.6High
CVSS 3.1 vector shape for CVE-2023-34337Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:C/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-326 · source CWE mapping

Inadequate Encryption Strength

Inadequate Encryption Strength represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.