# CVE-2020-7049: Other in n/a

> CSV injection in Nozomi Networks OS allows attackers to execute commands when exported data is opened in spreadsheet software.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mqxh-h263-vmrr

## What is CVE-2020-7049?

CVE-2020-7049 is a high-severity vulnerability in n/a, published on 30 Jun 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Nozomi Networks OS before 19.0.4 allows /#/network?tab=network_node_list.html CSV Injection.

Weakness: CWE-1236 (Improper Neutralization of Formula Elements in a CSV File)

## Which versions are affected by CVE-2020-7049?

It affects 1 product.


Products: Nozominetworks Guardian.

## How do I fix CVE-2020-7049?

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

## Is CVE-2020-7049 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15307](https://insights.sbomify.com/CVE-2020-15307/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7049 and fix it if it is affected.

What it is: CVE-2020-7049 is a high-severity vulnerability in n/a, published on 30 Jun 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-7049 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-2020-7049/ (Markdown: https://insights.sbomify.com/CVE-2020-7049/index.md)
```

## Sources

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

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