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

> Unauthenticated attackers can access the vendor account interface to read sensitive credentials and create new vendor accounts.

- **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 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g9jv-422p-3g6g

## What is CVE-2017-7312?

CVE-2017-7312 is a critical missing authorization vulnerability in n/a, published on 7 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Personify360 e-Business 7.5.2 through 7.6.1. When going to the /TabId/275 URI, anyone can add a vendor account or read existing vendor account data (including usernames and passwords).

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Personifycorp Personify360.

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

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

## Is CVE-2017-7312 being exploited?

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

Public exploit code:

- Personify360 7.5.2/7.6.1 - Improper Access Restrictions (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-7312 is a critical missing authorization vulnerability in n/a, published on 7 Jun 2017. 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-7312 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-7312/ (Markdown: https://insights.sbomify.com/CVE-2017-7312/index.md)
```

## Sources

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

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