# CVE-2023-27866: IBM Informix JDBC code execution

> Remote attackers can execute arbitrary code via JNDI injection in the IBM Informix JDBC Driver if LDAP URLs are not verified.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2023
- **Updated:** 28 Oct 2024
- **Also known as:** GHSA-m9fq-5h8w-v8jr

## What is CVE-2023-27866?

CVE-2023-27866 is a medium-severity code injection vulnerability in IBM Informix JDBC, published on 28 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Informix JDBC Driver 4.10 and 4.50 is susceptible to remote code execution attack via JNDI injection when driver code or the application using the driver do not verify supplied LDAP URL in Connect String.  IBM X-Force ID:  249511.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Ibm Informix Jdbc Driver.

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

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

## Is CVE-2023-27866 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-27866 is a medium-severity code injection vulnerability in IBM Informix JDBC, published on 28 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-27866 in the wild and no public exploit code.

Affected product: IBM Informix JDBC. 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-27866/ (Markdown: https://insights.sbomify.com/CVE-2023-27866/index.md)
```

## Sources

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

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