# CVE-2019-10123: SQL injection in n/a

> An anonymous attacker can execute arbitrary code via SQL injection in AIS ESEL-Server, leveraging default database credentials.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mc37-423h-gg8r

## What is CVE-2019-10123?

CVE-2019-10123 is a critical SQL injection vulnerability in n/a, published on 31 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL Injection in Advanced InfoData Systems (AIS) ESEL-Server 67 (which is the backend for the AIS logistics mobile app) allows an anonymous attacker to execute arbitrary code in the context of the user of the MSSQL database. The default user for the database is the 'sa' user.

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

## Which versions are affected by CVE-2019-10123?

It affects 1 product.


Products: Ais Logistic Software.

## How do I fix CVE-2019-10123?

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

## Is CVE-2019-10123 being exploited?

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

Public exploit code:

- AIS logistics ESEL-Server Unauth SQL Injection RCE (metasploit)
- AIS logistics ESEL-Server - Unauthenticated SQL Injection Remote Code Execution (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10123 and fix it if it is affected.

What it is: CVE-2019-10123 is a critical SQL injection vulnerability in n/a, published on 31 May 2019. 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-2019-10123 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-2019-10123/ (Markdown: https://insights.sbomify.com/CVE-2019-10123/index.md)
```

## Sources

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

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