# CVE-2023-52096: SQL injection in n/a

> Attackers can trigger SQL exceptions and corrupt transaction records by sending malformed OCPP timestamps to applications using the SteVe Community ocpp-jaxb library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 26 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-5798-fpq9-x4vx

## What is CVE-2023-52096?

CVE-2023-52096 is a high-severity SQL injection vulnerability in n/a, published on 26 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SteVe Community ocpp-jaxb before 0.0.8 generates invalid timestamps such as ones with month 00 in certain situations (such as when an application receives a StartTransaction Open Charge Point Protocol message with a timestamp parameter of 1000000). This may lead to a SQL exception in applications, and may undermine the integrity of transaction records.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Steve-Community Ocpp-Jaxb.

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

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

## Is CVE-2023-52096 being exploited?

There is no known exploitation of CVE-2023-52096 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-52096 is a high-severity SQL injection vulnerability in n/a, published on 26 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52096 in the wild and no public exploit code.

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-52096/ (Markdown: https://insights.sbomify.com/CVE-2023-52096/index.md)
```

## Sources

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

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