# CVE-2017-20150: challenge website sql injection

> An attacker can perform SQL injection on the challenge website to read or modify data, requiring a patch for remediation.

- **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:** 28 Dec 2022
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hqj5-w7wq-79fv

## What is CVE-2017-20150?

CVE-2017-20150 is a medium-severity SQL injection vulnerability in challenge website, published on 28 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in challenge website. It has been rated as critical. This issue affects some unknown processing. The manipulation leads to sql injection. The name of the patch is f1644b1d3502e5aa5284f31ea80d2623817f4d42. It is recommended to apply a patch to fix this issue. The identifier VDB-216989 was assigned to this vulnerability.

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

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

It affects 1 product.


Products: Challenge Website Project Challenge Website.

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

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

## Is CVE-2017-20150 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-20150 is a medium-severity SQL injection vulnerability in challenge website, published on 28 Dec 2022. 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-20150 in the wild and no public exploit code.

Affected product: challenge website. 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-20150/ (Markdown: https://insights.sbomify.com/CVE-2017-20150/index.md)
```

## Sources

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

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