AMI MegaRAC_SPx up to 12.7/13.5 BMC untrusted pointer dereference

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.6$0-$5k0.00

Summaryinfo

A vulnerability labeled as critical has been found in AMI MegaRAC_SPx up to 12.7/13.5. Affected by this issue is some unknown functionality of the component BMC. The manipulation results in untrusted pointer dereference. This vulnerability was named CVE-2023-34332. The attack needs to be approached locally. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as critical has been found in AMI MegaRAC_SPx up to 12.7/13.5. Affected is an unknown part of the component BMC. The manipulation with an unknown input leads to a untrusted pointer dereference vulnerability. CWE is classifying the issue as CWE-822. The product obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

AMI’s SPx contains a vulnerability in the BMC where an Attacker may cause an untrusted pointer to dereference by a local network. A successful exploitation of this vulnerability may lead to a loss of confidentiality, integrity, and/or availability.

The weakness was presented 01/10/2024. The advisory is available at 9443417.fs1.hubspotusercontent-na1.net. This vulnerability is traded as CVE-2023-34332 since 06/01/2023. The technical details are unknown and an exploit is not available.

Upgrading to version 13.6 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.8
VulDB Meta Temp Score: 7.6

VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 7.8
CNA Vector (AMI): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Untrusted pointer dereference
CWE: CWE-822
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: MegaRAC_SPx 13.6

Timelineinfo

06/01/2023 🔍
01/10/2024 +223 days 🔍
01/10/2024 +0 days 🔍
01/10/2024 +0 days 🔍

Sourcesinfo

Advisory: 9443417.fs1.hubspotusercontent-na1.net
Status: Confirmed

CVE: CVE-2023-34332 (🔍)
GCVE (CVE): GCVE-0-2023-34332
GCVE (VulDB): GCVE-100-250218

Entryinfo

Created: 01/10/2024 08:34
Changes: 01/10/2024 08:34 (49)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!