H3C Magic B1STW B1STV100R012 POST Request SetAPInfoById stack-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in H3C Magic B1STW B1STV100R012. This vulnerability affects the function SetAPInfoById of the component POST Request Handler. This manipulation causes stack-based overflow.
This vulnerability is handled as CVE-2023-34924. There is not any exploit available.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability has been found in H3C Magic B1STW B1STV100R012 and classified as problematic. Affected by this vulnerability is the function SetAPInfoById of the component POST Request Handler. The manipulation with an unknown input leads to a stack-based overflow vulnerability. The CWE definition for the vulnerability is CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). As an impact it is known to affect availability. The summary by CVE is:
H3C Magic B1STW B1STV100R012 was discovered to contain a stack overflow via the function SetAPInfoById. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted POST request.
The weakness was released 06/27/2023. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2023-34924 since 06/07/2023. Technical details of the vulnerability are known, but there is no available exploit.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-38964). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/07/2023 🔍06/27/2023 🔍
06/27/2023 🔍
01/10/2026 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2023-34924 (🔍)
GCVE (CVE): GCVE-0-2023-34924
GCVE (VulDB): GCVE-100-232411
EUVD: 🔍
Entry
Created: 06/27/2023 07:34 AMUpdated: 01/10/2026 11:05 AM
Changes: 06/27/2023 07:34 AM (39), 07/18/2023 08:15 PM (11), 01/10/2026 11:05 AM (16)
Complete: 🔍
Cache ID: 244:0E4:40
No comments yet. Languages: en.
Please log in to comment.