# CVE-2019-19735: Weak cryptography in n/a

> Attackers can brute-force weak password reset hashes to take over user accounts in YetiShare.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j9pc-f8q5-rxm8

## What is CVE-2019-19735?

CVE-2019-19735 is a critical vulnerability in n/a, published on 30 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

class.userpeer.php in MFScripts YetiShare 3.5.2 through 4.5.3 uses an insecure method of creating password reset hashes (based only on microtime), which allows an attacker to guess the hash and set the password within a few hours by bruteforcing.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort)

## Which versions are affected by CVE-2019-19735?

It affects 1 product.


Products: Mfscripts Yetishare.

## How do I fix CVE-2019-19735?

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

## Is CVE-2019-19735 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-20062](https://insights.sbomify.com/CVE-2019-20062/): Auth bypass in n/a (critical 9.8)
- [CVE-2019-20059](https://insights.sbomify.com/CVE-2019-20059/): SQL injection in n/a (high 8.8)
- [CVE-2019-19734](https://insights.sbomify.com/CVE-2019-19734/): SQL injection in n/a (high 8.8)
- [CVE-2019-19737](https://insights.sbomify.com/CVE-2019-19737/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2019-20060](https://insights.sbomify.com/CVE-2019-20060/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-19735 and fix it if it is affected.

What it is: CVE-2019-19735 is a critical vulnerability in n/a, published on 30 Dec 2019. 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-2019-19735 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-2019-19735/ (Markdown: https://insights.sbomify.com/CVE-2019-19735/index.md)
```

## Sources

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

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