# CVE-2017-16631: Missing authorization in n/a

> Guest users can change administrative passwords via IDOR in SapphireIMS, leading to privilege escalation and account takeover.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 11 Aug 2021
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vgv5-w2x4-8qf2

## What is CVE-2017-16631?

CVE-2017-16631 is a medium-severity missing authorization vulnerability in n/a, published on 11 Aug 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In SapphireIMS 4097_1, a guest user is able to change the password of an administrative user by utilizing an Insecure Direct Object Reference (IDOR) in the "Account Password Reset" functionality.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Sapphireims Sapphireims.

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

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

## Is CVE-2017-16631 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-25560](https://insights.sbomify.com/CVE-2020-25560/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-25563](https://insights.sbomify.com/CVE-2020-25563/): Missing authorization in n/a (critical 9.8)
- [CVE-2020-25565](https://insights.sbomify.com/CVE-2020-25565/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-25566](https://insights.sbomify.com/CVE-2020-25566/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-16630](https://insights.sbomify.com/CVE-2017-16630/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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