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

> Authenticated users can modify other users' profile data due to insufficient authorization checks in Pleasant Password Server.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 31 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qhmh-x535-r77m

## What is CVE-2017-17708?

CVE-2017-17708 is a medium-severity missing authorization vulnerability in n/a, published on 31 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Because of insufficient authorization checks it is possible for any authenticated user to change profile data of other users in Pleasant Password Server before 7.8.3.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Pleasantsolutions Pleasant Password Server.

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

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

## Is CVE-2017-17708 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-17707](https://insights.sbomify.com/CVE-2017-17707/): Missing authorization in n/a (high 8.1)
- [CVE-2023-27121](https://insights.sbomify.com/CVE-2023-27121/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17708 is a medium-severity missing authorization vulnerability in n/a, published on 31 Jul 2018. 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-17708 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-17708/ (Markdown: https://insights.sbomify.com/CVE-2017-17708/index.md)
```

## Sources

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

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