# CVE-2017-1000221: Opencast has Incorrect Permission Assignment

> Attackers can access restricted media recordings by exploiting flawed username matching in the search service, bypassing intended access controls.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** Yes
- **Published:** 17 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-hx44-c87v-p6xg

## What is CVE-2017-1000221?

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

### Official description

In Opencast 2.2.3 and older if user names overlap, the Opencast search service used for publication to the media modules and players will handle the access control incorrectly so that users only need to match part of the user name used for the access restriction. For example, a user with the role ROLE_USER will have access to recordings published only for ROLE_USER_X.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

2 open source packages ship an affected version, including org.opencastproject:opencast-kernel. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.opencastproject:opencast-kernel` | Maven | All versions | 2.2.4 |
| `org.opencastproject:opencast-kernel` | Maven | All versions | 2.2.4 |

Products: Apereo Opencast.

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

Upgrade org.opencastproject:opencast-kernel to 2.2.4 or later.

## Is CVE-2017-1000221 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-43821](https://insights.sbomify.com/CVE-2021-43821/): Files Accessible to External Parties in Opencast (critical 9.9)
- [CVE-2020-5206](https://insights.sbomify.com/CVE-2020-5206/): Authentication Bypass For Endpoints With Anonymous Access in OpenCast (high 8.7)
- [CVE-2021-32623](https://insights.sbomify.com/CVE-2021-32623/): Opencast vulnerable to billion laughs attack (XML bomb) (high 8.1)
- [CVE-2020-5229](https://insights.sbomify.com/CVE-2020-5229/): Opencast stores passwords using outdated MD5 hash algorithm (high 7.7)
- [CVE-2020-5230](https://insights.sbomify.com/CVE-2020-5230/): Opencast uses unsafe identifiers (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-1000221 is a medium-severity missing authorization vulnerability in n/a, published on 17 Nov 2017. 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-1000221 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.opencastproject:opencast-kernel (Maven): affected all versions; fixed in 2.2.4
- org.opencastproject:opencast-kernel (Maven): affected all versions; fixed in 2.2.4

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-1000221/ (Markdown: https://insights.sbomify.com/CVE-2017-1000221/index.md)
```

## Sources

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

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