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

> Attackers can take over any account, including administrators, by tampering with user ID parameters during profile updates due to lack of validation.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 7 Jan 2021
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8r69-p3hj-6c77

## What is CVE-2019-18642?

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

### Official description

Rock RMS version before 8.6 is vulnerable to account takeover by tampering with the user ID parameter in the profile update feature. The lack of validation and use of sequential user IDs allows any user to change account details of any other user. This vulnerability could be used to change the email address of another account, even the administrator account. Upon changing another account's email address, performing a password reset to the new email address could allow an attacker to take over any account.

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

It affects 1 product.


Products: Sparkdevnetwork Rock Rms.

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

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

## Is CVE-2019-18642 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-18643](https://insights.sbomify.com/CVE-2019-18643/): File upload in n/a (critical 9.8)
- [CVE-2019-18641](https://insights.sbomify.com/CVE-2019-18641/): Missing authorization in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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