Summary
The OpenSearch reporting plugin improperly controls tenancy access to reporting resources
An issue in the OpenSearch reporting plugin allows unintended access to private tenant resources like notebooks. The system did not properly check if the user was the resource author when accessing resources in a private tenant, leading to potential data being revealed.
Impacted versions <= 2.13
Workarounds
None
References
OpenSearch 2.14 is available for download at https://opensearch.org/versions/opensearch-2-14-0.html
The latest version of OpenSearch is available for download at https://opensearch.org/downloads.html
Impact
The lack of proper access control validation for private tenant resources in the OpenSearch observability and reporting plugins can lead to unintended data access. If an authorized user with observability or reporting roles is aware of another user's private tenant resource ID, such as a notebook, they can potentially read, modify, or take ownership of that resource, despite not being the original author, thus impacting the confidentiality and integrity of private tenant resources. The impact is confined to private tenant resources, where authorized users may gain inappropriate visibility into data intended to be private from other users within the same OpenSearch instance, potentially violating the intended separation of access. This issue does not alter the scope of access but highlights a flaw in the existing access control mechanisms.
CVE-2024-39900 has a CVSS score of 5.4 (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.14.0.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
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
The patches are included in OpenSearch 2.14
Frequently Asked Questions
- What is CVE-2024-39900? CVE-2024-39900 is a medium-severity security vulnerability in org.opensearch.plugin:opensearch-reports-scheduler (maven), affecting versions < 2.14.0.0. It is fixed in 2.14.0.0.
- How severe is CVE-2024-39900? CVE-2024-39900 has a CVSS score of 5.4 (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.
- Which versions of org.opensearch.plugin:opensearch-reports-scheduler are affected by CVE-2024-39900? org.opensearch.plugin:opensearch-reports-scheduler (maven) versions < 2.14.0.0 is affected.
- Is there a fix for CVE-2024-39900? Yes. CVE-2024-39900 is fixed in 2.14.0.0. Upgrade to this version or later.
- Is CVE-2024-39900 exploitable, and should I be worried? Whether CVE-2024-39900 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
- What actually determines whether CVE-2024-39900 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.
- How do I fix CVE-2024-39900? Upgrade
org.opensearch.plugin:opensearch-reports-schedulerto 2.14.0.0 or later.