# CVE-2017-17056: Cross-site request forgery in n/a

> Attackers can trick administrators into clicking crafted links to escalate privileges to administrator via CSRF in ZKTime Web Software.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v25g-pr9m-qxq7

## What is CVE-2017-17056?

CVE-2017-17056 is a high-severity vulnerability in n/a, published on 4 Dec 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The ZKTime Web Software 2.0.1.12280 allows the Administrator to elevate the privileges of the application user using a 'password_change()' function of the Modify Password component, reachable via the old_password, new_password1, and new_password2 parameters to the /accounts/password_change/ URI. An attacker takes advantage of this scenario and creates a crafted CSRF link to add himself as an administrator to the ZKTime Web Software. He then uses social engineering methods to trick the administrator into clicking the forged HTTP request. The request is executed and the attacker becomes the Administrator of the ZKTime Web Software. If the vulnerability is successfully exploited, then an attacker (who would be a normal user of the web application) can escalate his privileges and become the administrator of ZKTime Web Software.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Zkteco Zktime Web.

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

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

## Is CVE-2017-17056 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-13129](https://insights.sbomify.com/CVE-2017-13129/): Cross-site request forgery in n/a (high 8.0)
- [CVE-2017-14680](https://insights.sbomify.com/CVE-2017-14680/): Information disclosure in n/a (high 7.5)
- [CVE-2017-17057](https://insights.sbomify.com/CVE-2017-17057/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17056 is a high-severity vulnerability in n/a, published on 4 Dec 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-17056 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-17056/ (Markdown: https://insights.sbomify.com/CVE-2017-17056/index.md)
```

## Sources

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

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