# CVE-2023-40771: DataEase vulnerable to SQL injection

> Remote attackers can exploit SQL injection in DataEase to obtain sensitive information via crafted strings bypassing blacklist functions.

- **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:** 1 Sep 2023
- **Updated:** 1 Oct 2024
- **Also known as:** GHSA-8rv7-g772-pp3j

## What is CVE-2023-40771?

CVE-2023-40771 is a high-severity SQL injection vulnerability in Dataease Dataease, published on 1 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in DataEase v.1.18.9 allows a remote attacker to obtain sensitive information via a crafted string outside of the blacklist function.

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

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

2 open source packages ship an affected version, including io.dataease:dataease-plugin-common. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.dataease:dataease-plugin-common` | Maven | All versions to 1.18.9 | None |
| `io.dataease:dataease-plugin-common` | Maven | All versions to 1.18.9 | None |

Products: Dataease Dataease.

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

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

## Is CVE-2023-40771 being exploited?

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

## Other vulnerabilities in Dataease Dataease

- [CVE-2024-57707](https://insights.sbomify.com/CVE-2024-57707/): Code injection in n/a (critical 9.8)
- [CVE-2024-46997](https://insights.sbomify.com/CVE-2024-46997/): DataEase's H2 datasource has a remote command execution risk (critical 9.8)
- [CVE-2023-33963](https://insights.sbomify.com/CVE-2023-33963/): DataEase data source has deserialization vulnerability (critical 9.8)
- [CVE-2023-28437](https://insights.sbomify.com/CVE-2023-28437/): SQL injection vulnerability due to the keyword blacklist for defending against SQL injection will be bypassed (critical 9.8)
- [CVE-2022-39312](https://insights.sbomify.com/CVE-2022-39312/): Dataease Mysql Data Source JDBC Connection Parameters Not Verified Leads to Deserialization Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-40771 is a high-severity SQL injection vulnerability in Dataease Dataease, published on 1 Sep 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-40771 exists.

Affected packages and fixed versions:
- io.dataease:dataease-plugin-common (Maven): affected all versions up to 1.18.9; no fix listed
- io.dataease:dataease-plugin-common (Maven): affected all versions up to 1.18.9; no fix listed

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

## Sources

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

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