# CVE-2022-25225: SQL injection in Network Olympus

> An authenticated admin can inject SQL queries in Network Olympus, potentially leading to remote code execution on the underlying PostgreSQL database.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-32c2-v3m4-9q5j

## What is CVE-2022-25225?

CVE-2022-25225 is a high-severity SQL injection vulnerability in Network Olympus, published on 8 Mar 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Network Olympus version 1.8.0 allows an authenticated admin user to inject SQL queries in '/api/eventinstance' via the 'sqlparameter' JSON parameter. It is also possible to achieve remote code execution in the default installation (PostgreSQL) by exploiting this issue.

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

## Which versions are affected by CVE-2022-25225?

It affects 1 product.


Products: Softinventive Network Olympus.

## How do I fix CVE-2022-25225?

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

## Is CVE-2022-25225 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25225 and fix it if it is affected.

What it is: CVE-2022-25225 is a high-severity SQL injection vulnerability in Network Olympus, published on 8 Mar 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-25225 in the wild and no public exploit code.

Affected product: Network Olympus. 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-2022-25225/ (Markdown: https://insights.sbomify.com/CVE-2022-25225/index.md)
```

## Sources

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

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