# CVE-2019-17605: Business logic in n/a

> Attackers can take over other candidate accounts by modifying the candidate ID and password parameters in mass assignment requests.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f6p3-m24c-6r2v

## What is CVE-2019-17605?

CVE-2019-17605 is a high-severity vulnerability in n/a, published on 7 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A mass assignment vulnerability in eyecomms eyeCMS through 2019-10-15 allows any candidate to take over another candidate's account (by also exploiting CVE-2019-17604) via a modified candidate id and an additional password parameter. The outcome is that the password of this other candidate is changed.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Eyecomms Eyecms.

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

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

## Is CVE-2019-17605 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-17604](https://insights.sbomify.com/CVE-2019-17604/): Missing authorization in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-17605 is a high-severity vulnerability in n/a, published on 7 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-17605 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-17605/ (Markdown: https://insights.sbomify.com/CVE-2019-17605/index.md)
```

## Sources

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

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