# CVE-2017-1000164: Tine 2.0 version 2017.02.4 is vulnerable to XSS in the Addressbook resulting code execution and privilege escalation


- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-rjq4-c94x-623h

## What is CVE-2017-1000164?

CVE-2017-1000164 is a medium-severity vulnerability in n/a, published on 17 Nov 2017. 

### Official description

Tine 2.0 version 2017.02.4 is vulnerable to XSS in the Addressbook resulting code execution and privilege escalation

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Tine20 Tine 2.0.

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

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

## Is CVE-2017-1000164 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-14921](https://insights.sbomify.com/CVE-2017-14921/): Stored XSS vulnerability via IMG element at "Filename" of Filemanager in Tine 2.0 Community Edition before 2017.08.4 allows an authenticated (medium 5.4)
- [CVE-2017-14922](https://insights.sbomify.com/CVE-2017-14922/): Stored XSS vulnerability via IMG element at "History" of Profile, Calendar, Tasks, and CRM in Tine 2.0 Community Edition before 2017.08.4 al (medium 5.4)
- [CVE-2017-14923](https://insights.sbomify.com/CVE-2017-14923/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-1000164 is a medium-severity vulnerability in n/a, published on 17 Nov 2017. 
Exploitation: There is no known exploitation of CVE-2017-1000164 in the wild and no public exploit code.

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

## Sources

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

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