CVE-2017-1000221

CVE-2017-1000221 is a medium-severity incorrect permission assignment for critical resource vulnerability in org.opencastproject:opencast-kernel (maven), affecting versions < 2.2.4. It is fixed in 2.2.4.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Opencast has Incorrect Permission Assignment

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.

Impact

A file, directory, or other resource is assigned permissions that allow broader access than intended. Typical impact: unauthorized read, modification, or execution of the resource.

CVE-2017-1000221 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.2.4); upgrading removes the vulnerable code path.

Affected versions

org.opencastproject:opencast-kernel (< 2.2.4)

Security releases

org.opencastproject:opencast-kernel → 2.2.4 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

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

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2017-1000221? CVE-2017-1000221 is a medium-severity incorrect permission assignment for critical resource vulnerability in org.opencastproject:opencast-kernel (maven), affecting versions < 2.2.4. It is fixed in 2.2.4. A file, directory, or other resource is assigned permissions that allow broader access than intended.
  2. How severe is CVE-2017-1000221? CVE-2017-1000221 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of org.opencastproject:opencast-kernel are affected by CVE-2017-1000221? org.opencastproject:opencast-kernel (maven) versions < 2.2.4 is affected.
  4. Is there a fix for CVE-2017-1000221? Yes. CVE-2017-1000221 is fixed in 2.2.4. Upgrade to this version or later.
  5. Is CVE-2017-1000221 exploitable, and should I be worried? Whether CVE-2017-1000221 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2017-1000221 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2017-1000221? Upgrade org.opencastproject:opencast-kernel to 2.2.4 or later.

Other vulnerabilities in org.opencastproject:opencast-kernel

Stop the waste.
Protect your environment with Kodem.