Dalmann OCPP.Core up to 1.1.x Open Charge Point Protocol chargePointVendor denial of service ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Dalmann OCPP.Core up to 1.1.x. It has been rated as problematic. This issue affects some unknown processing of the component Open Charge Point Protocol. The manipulation of the argument chargePointVendor leads to denial of service. This vulnerability is listed as CVE-2023-49955. There is no available exploit. It is still unclear if this vulnerability genuinely exists. Upgrading the affected component is advised.
Details
A vulnerability was found in Dalmann OCPP.Core up to 1.1.x and classified as problematic. This issue affects an unknown function of the component Open Charge Point Protocol. The manipulation of the argument chargePointVendor with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability. The summary by CVE is:
An issue was discovered in Dalmann OCPP.Core before 1.2.0 for OCPP (Open Charge Point Protocol) for electric vehicles. It does not validate the length of the chargePointVendor field in a BootNotification message, potentially leading to server instability and a denial of service when processing excessively large inputs. NOTE: the vendor's perspective is "OCPP.Core is intended for use in a protected environment/network."
The weakness was presented 12/07/2023 as 32. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2023-49955 since 12/03/2023. Technical details of the vulnerability are known, but there is no available exploit.
The real existence of this vulnerability is still doubted at the moment.
Upgrading to version 1.2.0 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
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: Denial of serviceCWE: CWE-404
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: OCPP.Core 1.2.0
Timeline
12/03/2023 🔍12/07/2023 🔍
12/07/2023 🔍
12/30/2023 🔍
Sources
Advisory: 32Status: Confirmed
Disputed: 🔍
CVE: CVE-2023-49955 (🔍)
GCVE (CVE): GCVE-0-2023-49955
GCVE (VulDB): GCVE-100-247163
Entry
Created: 12/07/2023 14:24Updated: 12/30/2023 17:15
Changes: 12/07/2023 14:24 (43), 12/30/2023 17:15 (11)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.