Charging interruption via unchecked transaction identifier
Published Dec 7, 2023 · Updated Aug 2, 2024
Denial of service in Dalmann OCPP.Core before 1.3.0 allows remote attackers to interrupt charging via a StopTransaction message. The OCPP server accepts an arbitrary transactionId instead of requiring the identifier assigned when the active transaction started, then stops that transaction. The attack requires network access to the OCPP endpoint and an active transaction; the bounded consequence is premature charging termination.
Summary
What happened
Denial of service in Dalmann OCPP.Core before 1.3.0 allows remote attackers to interrupt charging via a StopTransaction message. The OCPP server accepts an arbitrary transactionId instead of requiring the identifier assigned when the active transaction started, then stops that transaction. The attack requires network access to the OCPP endpoint and an active transaction; the bounded consequence is premature charging termination.
The record
- CVE
- CVE-2023-49956
- Published
- Dec 7, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T0814
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 7, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Random transaction identifier reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo