# CVE-2016-2171: Missing authorization in n/a

> Remote attackers can add, edit, or delete users via the REST API due to improper access restrictions in the User Manager service.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 Apr 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q4gp-393m-x83p

## What is CVE-2016-2171?

CVE-2016-2171 is a high-severity missing authorization vulnerability in n/a, published on 11 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The User Manager service in Apache Jetspeed before 2.3.1 does not properly restrict access using Jetspeed Security, which allows remote attackers to (1) add, (2) edit, or (3) delete users via the REST API.

Weakness: CWE-264

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

It affects 1 product.


Products: Apache Jetspeed.

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

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

## Is CVE-2016-2171 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-32533](https://insights.sbomify.com/CVE-2022-32533/): Apache Portals Jetspeed XSS, CSRF, SSRF, and XXE issues (critical 9.8)
- [CVE-2016-0710](https://insights.sbomify.com/CVE-2016-0710/): Apache Jetspeed vulnerable to SQL Injection (high 8.8)
- [CVE-2016-0709](https://insights.sbomify.com/CVE-2016-0709/): Path Traversal in Apache Jetspeed (high 7.2)
- [CVE-2016-0711](https://insights.sbomify.com/CVE-2016-0711/): Apache Jetspeed vulnerable to Cross-site Scripting (medium 6.1)
- [CVE-2016-0712](https://insights.sbomify.com/CVE-2016-0712/): Cross-site Scripting in Apache Jetspeed (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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