# CVE-2017-16629: Information disclosure in n/a

> Attackers can enumerate valid usernames in SapphireIMS by observing distinct error messages returned during login attempts.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 11 Aug 2021
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f4x9-gw7p-923p

## What is CVE-2017-16629?

CVE-2017-16629 is a high-severity vulnerability in n/a, published on 11 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In SapphireIMS 4097_1, it is possible to guess the registered/active usernames of the software from the errors it gives out for each type of user on the Login form. For "Incorrect User" - it gives an error "The application failed to identify the user. Please contact administrator for help." For "Correct User and Incorrect Password" - it gives an error "Authentication failed. Please login again."

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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

It affects 1 product.


Products: Sapphireims Sapphireims.

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

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

## Is CVE-2017-16629 being exploited?

There is no known exploitation of CVE-2017-16629 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-16629 and fix it if it is affected.

What it is: CVE-2017-16629 is a high-severity vulnerability in n/a, published on 11 Aug 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-2017-16629 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-16629/ (Markdown: https://insights.sbomify.com/CVE-2017-16629/index.md)
```

## Sources

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

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