# CVE-2017-17097: Weak cryptography in n/a

> Remote attackers can take over admin accounts by predicting date-based passwords generated during unauthenticated password resets.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 2 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pqjh-4hfv-gw8h

## What is CVE-2017-17097?

CVE-2017-17097 is a critical vulnerability in n/a, published on 2 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

gps-server.net GPS Tracking Software (self hosted) 2.x has a password reset procedure that immediately resets passwords upon an unauthenticated request, and then sends e-mail with a predictable (date-based) password to the admin, which makes it easier for remote attackers to obtain access by predicting this new password. This is related to the use of gmdate for password creation in fn_connect.php.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

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

It affects 1 product.


Products: Gps-Server Gps Tracking Software.

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

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

## Is CVE-2017-17097 being exploited?

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

Public exploit code:

- gps-server.net GPS Tracking Software < 3.1 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-17098](https://insights.sbomify.com/CVE-2017-17098/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17097 is a critical vulnerability in n/a, published on 2 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-17097 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-17097/ (Markdown: https://insights.sbomify.com/CVE-2017-17097/index.md)
```

## Sources

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

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