CVE-2017-20150: A vulnerability was found in challenge website

Q: How do I fix CVE-2017-20150?

challenge website: upgrade to 2017-01-24. Exact commands for each OS are on this page.

Q: Is CVE-2017-20150 being exploited?

CVE-2017-20150 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2017-20150 affect?

CVE-2017-20150 affects challenge website. Severity is medium (CVSS 5.5). 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 rec

Q: How urgent is CVE-2017-20150?

Priority 33/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

CVE-2017-20150 is a medium-severity flaw (CVSS 5.5) affecting challenge website. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.7% (top 46%)
CISA exploited list	No
Weakness	CWE-89
Published	2022-12-28
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: challenge website project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-12-28 19:15 UTCPublished CVE record published
2026-06-17 01:15 UTCUpdated Record last modified

challenge website project challenge website UPGRADE

Affected: < 2017-01-24

Fixed in: 2017-01-24

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy challenge-website || rpm -q challenge-website || challenge-website --version

2. UPGRADE to 2017-01-24 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade challenge-website

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade challenge-website

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-20150?

challenge website: upgrade to 2017-01-24. Exact commands for each OS are on this page.

Is CVE-2017-20150 being exploited?

CVE-2017-20150 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-20150 affect?

CVE-2017-20150 affects challenge website. Severity is medium (CVSS 5.5). 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 rec

How urgent is CVE-2017-20150?

Priority 33/100. No elevated risk signals yet.

References

← Back to latest CVEs