# CVE-2018-10054: Improper Input Validation in Datomic

> Remote attackers can execute arbitrary Java code via the CREATE ALIAS command in the H2 database, affecting applications using this library.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9pf8-qqhm-7w64

## What is CVE-2018-10054?

CVE-2018-10054 is a high-severity code injection vulnerability in n/a, published on 11 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

H2 1.4.197, as used in Datomic before 0.9.5697 and other products, allows remote code execution because CREATE ALIAS can execute arbitrary Java code. NOTE: the vendor's position is "h2 is not designed to be run outside of a secure environment."

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-10054?

2 open source packages ship an affected version, including com.datomic:datomic-free. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.datomic:datomic-free` | Maven | All versions | 0.9.5697 |
| `com.datomic:datomic-free` | Maven | All versions | 0.9.5697 |

Products: Cognitect Datomic, H2database H2.

## How do I fix CVE-2018-10054?

Upgrade com.datomic:datomic-free to 0.9.5697 or later.

## Is CVE-2018-10054 being exploited?

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

Public exploit code:

- H2 Web Interface Create Alias RCE (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10054 and fix it if it is affected.

What it is: CVE-2018-10054 is a high-severity code injection vulnerability in n/a, published on 11 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-10054 exists.

Affected packages and fixed versions:
- com.datomic:datomic-free (Maven): affected all versions; fixed in 0.9.5697
- com.datomic:datomic-free (Maven): affected all versions; fixed in 0.9.5697

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

## Sources

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

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