{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-23933 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-23933 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-23933 is a medium-severity missing authorization vulnerability in opensearch-project anomaly-detection, published on 3 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-23933 and fix it if it is affected.\n\nWhat it is: CVE-2023-23933 is a medium-severity missing authorization vulnerability in opensearch-project anomaly-detection, published on 3 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-23933 in the wild and no public exploit code.\n\nAffected product: opensearch-project anomaly-detection. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-23933/ (Markdown: https://insights.sbomify.com/CVE-2023-23933/index.md)","id":"CVE-2023-23933","markdown":"https://insights.sbomify.com/CVE-2023-23933/index.md","name":"CVE-2023-23933","record":{"aliases":["GHSA-47qw-jwpx-pp4c"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenSearch Anomaly Detection","requires_auth":"low_privilege","summary":"Authenticated users with the Anomaly Detector role can bypass field-level restrictions to read aggregated numerical data from restricted indexes.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"opensearch","vendor":"amazon"}],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"OpenSearch Anomaly Detection identifies atypical data and receives automatic notifications. There is an issue with the application of document and field level restrictions in the Anomaly Detection plugin, where users with the Anomaly Detector role can read aggregated numerical data (e.g. averages, sums) of fields that are otherwise restricted to them. This issue only affects authenticated users who were previously granted read access to the indexes containing the restricted fields. This issue has been patched in versions 1.3.8 and 2.6.0. There are no known workarounds for this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Issue in Anomaly Detection with document and field level rules in numerical feature aggregations","id":"CVE-2023-23933","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Wrkzeug's incorrect parsing of nameless cookies leads to __Host- cookies bypass","id":"CVE-2023-23934"},"packages":[],"prev":{"headline":"Specially crafted RTPS message may cause an OpenDDS application to crash","id":"CVE-2023-23932"},"products":["anomaly-detection"],"published":"2023-02-03","related":[{"cvss_score":8.8,"headline":"Unsafe YAML deserialization in opensearch-ruby","id":"CVE-2022-31115","kev_date_added":null,"published":"2022-06-30"},{"cvss_score":8.3,"headline":"OpenSearch 3.2.0 - Nested Boolean/Disjunction asymmetric DoS","id":"CVE-2025-9624","kev_date_added":null,"published":"2025-11-25"},{"cvss_score":7.5,"headline":"OpenSearch vulnerable to Improper Authorization of Index Containing Sensitive Information","id":"CVE-2022-35980","kev_date_added":null,"published":"2022-08-12"},{"cvss_score":6.3,"headline":"Issue with fine-grained access control of indices backing data streams","id":"CVE-2022-41918","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":5.7,"headline":"Field-level security issue with .keyword fields in OpenSearch","id":"CVE-2023-23613","kev_date_added":null,"published":"2023-01-24"},{"cvss_score":5.4,"headline":"OpenSearch Issue with tenant read-only permissions","id":"CVE-2023-45807","kev_date_added":null,"published":"2023-10-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-10","vendors":["opensearch-project"]},"summary":"Authenticated users with the Anomaly Detector role can bypass field-level restrictions to read aggregated numerical data from restricted indexes.","url":"https://insights.sbomify.com/CVE-2023-23933/"}