References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to nvd@nist.gov.

Known Affected Software Configurations Switch to CPE 2.2

Change History

https://github.com/dallmann-consulting/OCPP.Core/issues/35

NIST AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

NIST AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

NIST AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

NIST NVD-CWE-noinfo

OR
     *cpe:2.3:a:dallmann-consulting:open_charge_point_protocol:*:*:*:*:*:*:*:* versions up to (excluding) 1.3.0

https://github.com/dallmann-consulting/OCPP.Core/issues/35 No Types Assigned

https://github.com/dallmann-consulting/OCPP.Core/issues/35 Exploit, Issue Tracking, Vendor Advisory

An issue was discovered in Dalmann OCPP.Core before 1.3.0 for OCPP (Open Charge Point Protocol) for electric vehicles. It permits multiple transactions with the same connectorId and idTag, contrary to the expected ConcurrentTx status. This could result in critical transaction management and billing errors. NOTE: the vendor's perspective is "Imagine you've got two cars in your family and want to charge both in parallel on the same account/token? Why should that be rejected?"

MITRE https://github.com/dallmann-consulting/OCPP.Core/issues/35 [No types assigned]