# CVE-2021-41390: Other in n/a

> Attacker can inject malicious CSV formulas into Ericsson ECM User Profile Management, potentially leading to code execution when exported.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-88x2-v352-g224

## What is CVE-2021-41390?

CVE-2021-41390 is a high-severity vulnerability in n/a, published on 17 Sep 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

In Ericsson ECM before 18.0, it was observed that Security Provider Endpoint in the User Profile Management Section is vulnerable to CSV Injection.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Ericsson Enterprise Content Management.

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

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

## Is CVE-2021-41390 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-41391](https://insights.sbomify.com/CVE-2021-41391/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-41390 is a high-severity vulnerability in n/a, published on 17 Sep 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-41390 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-41390/ (Markdown: https://insights.sbomify.com/CVE-2021-41390/index.md)
```

## Sources

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

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