Security 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?"
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2023-49957
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 05:49 UTC · Revision 1
Source evidence
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?"
osv:CVE-2023-49957
Complete source record
{
"id": "9af55ec586d3d020eac1b6d4b5c7acd8867766680f3572ec7ecf86647449e45f",
"url": "https://osv.dev/vulnerability/CVE-2023-49957",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "CVE-2023-49957",
"summary": "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?\"",
"evidence": "osv:CVE-2023-49957",
"products": [],
"severity": "unknown",
"structured": {
"id": "CVE-2023-49957",
"aliases": [
"CVE-2023-49957"
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/dallmann-consulting/ocpp.core",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "116f82a43698deaa65b4e5042c1a4c98523537d2"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "1.3.0"
}
],
"source": "DESCRIPTION"
},
{
"cpe": "cpe:2.3:a:dallmann-consulting:open_charge_point_protocol:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "1.3.0"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"V1.2.0",
"V1.1.0",
"0.1"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-49957.json"
}
}
],
"modified": "2026-10-28T02:30:43.161191592Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/49xxx/CVE-2023-49957.json",
"https://nvd.nist.gov/vuln/detail/CVE-2023-49957",
"https://github.com/dallmann-consulting/OCPP.Core/issues/35"
],
"provider_metadata": {
"cna_assigner": "mitre",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/49xxx/CVE-2023-49957.json"
}
},
"related_cves": [
{
"value": "CVE-2023-49957",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 510836,
"published_at": "2023-12-07T00:00:00+00:00"
}