# CVE-2021-28969: SQL injection in n/a

> Remote authenticated users can perform SQL injection via the email search feature, potentially accessing or modifying data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 1 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-f4g4-33pr-68pc

## What is CVE-2021-28969?

CVE-2021-28969 is a medium-severity SQL injection vulnerability in n/a, published on 1 Apr 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

eMPS 9.0.1.923211 on FireEye EX 3500 devices allows remote authenticated users to conduct SQL injection attacks via the sort_by parameter to the email search feature. According to the vendor, the issue is fixed in 9.0.3. NOTE: this is different from CVE-2020-25034 and affects newer versions of the software.

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

## Which versions are affected by CVE-2021-28969?

It affects 1 product.


Products: Fireeye Email Malware Protection System.

## How do I fix CVE-2021-28969?

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

## Is CVE-2021-28969 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-28970](https://insights.sbomify.com/CVE-2021-28970/): SQL injection in n/a (medium 6.5)
- [CVE-2020-25034](https://insights.sbomify.com/CVE-2020-25034/): SQL injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-28969 and fix it if it is affected.

What it is: CVE-2021-28969 is a medium-severity SQL injection vulnerability in n/a, published on 1 Apr 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-28969 in the wild and no public exploit code.

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

## Sources

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

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