{"answers":{"affected":"4 open source packages ship an affected version, including org.opensearch.plugin:opensearch-security. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-23612 in the wild and no public exploit code.","fix":"Upgrade org.opensearch.plugin:opensearch-security to a fixed version for your release line: 1.3.8 or 2.5.0.","what":"CVE-2023-23612 is a medium-severity authentication bypass vulnerability in opensearch-project security, published on 24 Jan 2023. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-23612 and fix it if it is affected.\n\nWhat it is: CVE-2023-23612 is a medium-severity authentication bypass vulnerability in opensearch-project security, published on 24 Jan 2023. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-23612 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.opensearch.plugin:opensearch-security (Maven): affected all versions; fixed in 1.3.8\n- org.opensearch.plugin:opensearch-security (Maven): affected all versions; fixed in 1.3.8\n- org.opensearch.plugin:opensearch-security (Maven): affected from 2.0.0; fixed in 2.5.0\n- org.opensearch.plugin:opensearch-security (Maven): affected from 2.0.0; fixed in 2.5.0\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-23612/ (Markdown: https://insights.sbomify.com/CVE-2023-23612/index.md)","id":"CVE-2023-23612","markdown":"https://insights.sbomify.com/CVE-2023-23612/index.md","name":"CVE-2023-23612","record":{"aliases":["GHSA-864v-6qj7-62qj","UBUNTU-CVE-2023-23612"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"OpenSearch search engine","requires_auth":"high_privilege","summary":"Authenticated users can claim unauthorized roles by exploiting whitespace trimming in JWT processing, leading to privilege escalation.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"opensearch","vendor":"amazon"}],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"OpenSearch is an open source distributed and RESTful search engine. OpenSearch uses JWTs to store role claims obtained from the Identity Provider (IdP) when the authentication backend is SAML or OpenID Connect. There is an issue in how those claims are processed from the JWTs where the leading and trailing whitespace is trimmed, allowing users to potentially claim roles they are not assigned to if any role matches the whitespace-stripped version of the roles they are a member of. This issue is only present for authenticated users, and it requires either the existence of roles that match, not considering leading/trailing whitespace, or the ability for users to create said matching roles. In addition, the Identity Provider must allow leading and trailing spaces in role names. OpenSearch 1.0.0-1.3.7 and 2.0.0-2.4.1 are affected. Users are advised to upgrade to OpenSearch 1.3.8 or 2.5.0. There are no known workarounds for this issue.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Issue with whitespace in JWT roles in OpenSearch","id":"CVE-2023-23612","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"auth_bypass","year":"2023"},"n_packages":4,"n_references":2,"next":{"headline":"Field-level security issue with .keyword fields in OpenSearch","id":"CVE-2023-23613"},"packages":[{"ecosystem":"Maven","fixed":["1.3.8"],"introduced":["0"],"last_affected":[],"package":"org.opensearch.plugin:opensearch-security","purl":null,"source":"GHSA-864v-6qj7-62qj"},{"ecosystem":"Maven","fixed":["1.3.8"],"introduced":["0"],"last_affected":[],"package":"org.opensearch.plugin:opensearch-security","purl":"pkg:maven/org.opensearch.plugin/opensearch-security","source":"GHSA-864v-6qj7-62qj"},{"ecosystem":"Maven","fixed":["2.5.0"],"introduced":["2.0.0"],"last_affected":[],"package":"org.opensearch.plugin:opensearch-security","purl":null,"source":"GHSA-864v-6qj7-62qj"},{"ecosystem":"Maven","fixed":["2.5.0"],"introduced":["2.0.0"],"last_affected":[],"package":"org.opensearch.plugin:opensearch-security","purl":"pkg:maven/org.opensearch.plugin/opensearch-security","source":"GHSA-864v-6qj7-62qj"}],"prev":{"headline":"xblock-lti-consumer contain Missing Authorization in Grade Pass Back Implementation","id":"CVE-2023-23611"},"products":["security"],"published":"2023-01-24","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":"Issue in Anomaly Detection with document and field level rules in numerical feature aggregations","id":"CVE-2023-23933","kev_date_added":null,"published":"2023-02-03"},{"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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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 can claim unauthorized roles by exploiting whitespace trimming in JWT processing, leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2023-23612/"}