# CVE-2016-4505: Privilege escalation in n/a

> Remote authenticated users can modify arbitrary passwords on RDM Intuitive 650 TDB Controllers, leading to privilege escalation and account takeover.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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 May 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-ffrh-8696-mw58

## What is CVE-2016-4505?

CVE-2016-4505 is a high-severity vulnerability in n/a, published on 31 May 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Resource Data Management (RDM) Intuitive 650 TDB Controller devices before 2.1.24 allow remote authenticated users to modify arbitrary passwords via unspecified vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2016-4505?

It affects 1 product.


Products: Resourcedm Intuitive 650 Tdb Controller.

## How do I fix CVE-2016-4505?

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

## Is CVE-2016-4505 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-4506](https://insights.sbomify.com/CVE-2016-4506/): Cross-site request forgery in n/a (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-4505 and fix it if it is affected.

What it is: CVE-2016-4505 is a high-severity vulnerability in n/a, published on 31 May 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-4505 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-2016-4505/ (Markdown: https://insights.sbomify.com/CVE-2016-4505/index.md)
```

## Sources

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

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