{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-49957 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-49957 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-49957 is a high-severity vulnerability in n/a, published on 7 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-49957 and fix it if it is affected.\n\nWhat it is: CVE-2023-49957 is a high-severity vulnerability in n/a, published on 7 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-49957 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-49957/ (Markdown: https://insights.sbomify.com/CVE-2023-49957/index.md)","id":"CVE-2023-49957","markdown":"https://insights.sbomify.com/CVE-2023-49957/index.md","name":"CVE-2023-49957","record":{"aliases":["GHSA-2pjv-w5q5-2v83"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","other"],"network_reachable":"yes","non_default_config":false,"product_category":"EV charging software","requires_auth":"none","summary":"Attackers can initiate multiple concurrent charging transactions on a single connector, causing billing errors and transaction management issues in EV charging systems.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"open_charge_point_protocol","vendor":"dallmann-consulting"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[],"description":"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?\"","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Business logic in n/a","id":"CVE-2023-49957","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Business logic in n/a","id":"CVE-2023-49958"},"packages":[],"prev":{"headline":"Business logic in n/a","id":"CVE-2023-49956"},"products":["n/a"],"published":"2023-12-07","related":[{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2023-49955","kev_date_added":null,"published":"2023-12-07"},{"cvss_score":7.5,"headline":"Business logic in n/a","id":"CVE-2023-49956","kev_date_added":null,"published":"2023-12-07"},{"cvss_score":7.5,"headline":"Business logic in n/a","id":"CVE-2023-49958","kev_date_added":null,"published":"2023-12-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"Attackers can initiate multiple concurrent charging transactions on a single connector, causing billing errors and transaction management issues in EV charging systems.","url":"https://insights.sbomify.com/CVE-2023-49957/"}