# CVE-2017-20163: Red Snapper NView Session.php mutate sql injection

> SQL injection in Red Snapper NView allows attackers to manipulate database queries via the session argument in Session.php.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jan 2023
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-249j-645x-c97w

## What is CVE-2017-20163?

CVE-2017-20163 is a medium-severity SQL injection vulnerability in Red Snapper NView, published on 5 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been found in Red Snapper NView and classified as critical. This vulnerability affects the function mutate of the file src/Session.php. The manipulation of the argument session leads to sql injection. The name of the patch is cbd255f55d476b29e5680f66f48c73ddb3d416a8. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-217516.

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

## Which versions are affected by CVE-2017-20163?

It affects 1 product.


Products: Nview Project Nview.

## How do I fix CVE-2017-20163?

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

## Is CVE-2017-20163 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-20163 and fix it if it is affected.

What it is: CVE-2017-20163 is a medium-severity SQL injection vulnerability in Red Snapper NView, published on 5 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-20163 in the wild and no public exploit code.

Affected product: Red Snapper NView. 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-2017-20163/ (Markdown: https://insights.sbomify.com/CVE-2017-20163/index.md)
```

## Sources

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

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