# CVE-2017-20179: InSTEDD Pollit tour_controller.rb TourController Privilege Escalation


- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Feb 2023
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q9c5-cc49-h24w

## What is CVE-2017-20179?

CVE-2017-20179 is a medium-severity vulnerability in InSTEDD Pollit, published on 21 Feb 2023. 

### Official description

A vulnerability was found in InSTEDD Pollit 2.3.1. It has been rated as critical. This issue affects the function TourController of the file app/controllers/tour_controller.rb. The manipulation leads to an unknown weakness. The attack may be initiated remotely. Upgrading to version 2.3.2 is able to address this issue. The patch is named 6ef04f8b5972d5f16f8b86f8b53f62fac68d5498. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-221507.

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

It affects 1 product.


Products: Instedd Pollit.

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

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

## Is CVE-2017-20179 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-20179 is a medium-severity vulnerability in InSTEDD Pollit, published on 21 Feb 2023. 
Exploitation: There is no known exploitation of CVE-2017-20179 in the wild and no public exploit code.

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

## Sources

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

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