# CVE-2021-32704: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in dhis2-core > Authenticated users can exploit SQL injection in the trackedEntityInstances API to read, edit, and delete data in DHIS2 instances. - **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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:** No - **Published:** 24 Jun 2021 - **Updated:** 3 Aug 2024 - **Also known as:** GHSA-fj38-585h-hxgj ## What is CVE-2021-32704? CVE-2021-32704 is a high-severity SQL injection vulnerability in dhis2-core, published on 24 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description DHIS 2 is an information system for data capture, management, validation, analytics and visualization. A SQL injection security vulnerability has been found in specific versions of DHIS2. This vulnerability affects the /api/trackedEntityInstances API endpoint in DHIS2 versions 2.34.4, 2.35.2, 2.35.3, 2.35.4, and 2.36.0. Earlier versions, such as 2.34.3 and 2.35.1 and all versions 2.33 and older are unaffected. The system is vulnerable to attack only from users that are logged in to DHIS2, and there is no known way of exploiting the vulnerability without first being logged in as a DHIS2 user. A successful exploit of this vulnerability could allow the malicious user to read, edit and delete data in the DHIS2 instance. There are no known exploits of the security vulnerabilities addressed by these patch releases. However, we strongly recommend that all DHIS2 implementations using versions 2.34, 2.35 and 2.36 install these patches as soon as possible. There is no straightforward known workaround for DHIS2 instances using the Tracker functionality other than upgrading the affected DHIS2 server to one of the patches in which this vulnerability has been fixed. For implementations which do NOT use Tracker functionality, it may be possible to block all network access to POST to the /api/trackedEntityInstance endpoint as a temporary workaround while waiting to upgrade. Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command) ## Which versions are affected by CVE-2021-32704? It affects 1 product. Products: Dhis2 Dhis 2. ## How do I fix CVE-2021-32704? No fix has been published for CVE-2021-32704 yet. Limit exposure of the affected software until one is available. ## Is CVE-2021-32704 being exploited? There is no known exploitation of CVE-2021-32704 in the wild and no public exploit code. ## Other vulnerabilities in dhis2-core - [CVE-2022-24848](https://insights.sbomify.com/CVE-2022-24848/): SQL Injection in DHIS2's in OrgUnit program association (high 8.8) - [CVE-2021-39179](https://insights.sbomify.com/CVE-2021-39179/): SQL Injection in DHIS2 Tracker API (high 8.8) - [CVE-2021-41187](https://insights.sbomify.com/CVE-2021-41187/): SQL Injection in DHIS2 Tracker API (high 8.1) - [CVE-2023-31138](https://insights.sbomify.com/CVE-2023-31138/): DHIS2 Core vulnerable to Improper Access Control with PATCH requests (high 7.1) - [CVE-2022-41948](https://insights.sbomify.com/CVE-2022-41948/): Privilege Chaining with the user admin role in dhis2-core (medium 6.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-32704 and fix it if it is affected. What it is: CVE-2021-32704 is a high-severity SQL injection vulnerability in dhis2-core, published on 24 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2021-32704 in the wild and no public exploit code. Affected product: dhis2-core. 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-2021-32704/ (Markdown: https://insights.sbomify.com/CVE-2021-32704/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-32704 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-32704 - OSV: https://osv.dev/vulnerability/CVE-2021-32704 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-32704/ Summaries are generated and may contain mistakes; the official description above is the record.