# CVE-2023-49958: Business logic in n/a

> Attackers can alter transaction records in Dalmann OCPP.Core by sending StartTransaction messages with duplicate or arbitrary properties.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Dec 2023
- **Updated:** 9 Oct 2024
- **Also known as:** GHSA-8mqw-jpwq-w6mr

## What is CVE-2023-49958?

CVE-2023-49958 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.

### Official description

An issue was discovered in Dalmann OCPP.Core through 1.2.0 for OCPP (Open Charge Point Protocol) for electric vehicles. The server processes mishandle StartTransaction messages containing additional, arbitrary properties, or duplicate properties. The last occurrence of a duplicate property is accepted. This could be exploited to alter transaction records or impact system integrity.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2023-49958?

It affects 1 product.


Products: Dallmann-Consulting Open Charge Point Protocol.

## How do I fix CVE-2023-49958?

No fix has been published for CVE-2023-49958 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-49958 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49958 exists.

## Other vulnerabilities in n/a

- [CVE-2023-49955](https://insights.sbomify.com/CVE-2023-49955/): Denial of service in n/a (high 7.5)
- [CVE-2023-49956](https://insights.sbomify.com/CVE-2023-49956/): Business logic in n/a (high 7.5)
- [CVE-2023-49957](https://insights.sbomify.com/CVE-2023-49957/): Business logic in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49958 and fix it if it is affected.

What it is: CVE-2023-49958 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49958 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-49958/ (Markdown: https://insights.sbomify.com/CVE-2023-49958/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-49958
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-49958
- OSV: https://osv.dev/vulnerability/CVE-2023-49958

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-49958/
Summaries are generated and may contain mistakes; the official description above is the record.