gsd-2023-23612
Vulnerability from gsd
Modified
2023-12-13 01:20
Details
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.
Aliases
Aliases



{
  "GSD": {
    "alias": "CVE-2023-23612",
    "id": "GSD-2023-23612"
  },
  "gsd": {
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "osvSchema": {
      "aliases": [
        "CVE-2023-23612"
      ],
      "details": "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.",
      "id": "GSD-2023-23612",
      "modified": "2023-12-13T01:20:49.467713Z",
      "schema_version": "1.4.0"
    }
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "security-advisories@github.com",
        "ID": "CVE-2023-23612",
        "STATE": "PUBLIC"
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "security",
                    "version": {
                      "version_data": [
                        {
                          "version_affected": "=",
                          "version_value": "\u003e= 2.0.0, \u003c 2.5.0"
                        },
                        {
                          "version_affected": "=",
                          "version_value": "\u003c 1.3.8"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "opensearch-project"
            }
          ]
        }
      },
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "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."
          }
        ]
      },
      "impact": {
        "cvss": [
          {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "LOW",
            "baseScore": 4.7,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "HIGH",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L",
            "version": "3.1"
          }
        ]
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "cweId": "CWE-287",
                "lang": "eng",
                "value": "CWE-287: Improper Authentication"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "https://github.com/opensearch-project/OpenSearch/releases/tag/2.5.0",
            "refsource": "MISC",
            "url": "https://github.com/opensearch-project/OpenSearch/releases/tag/2.5.0"
          },
          {
            "name": "https://github.com/opensearch-project/security/security/advisories/GHSA-864v-6qj7-62qj",
            "refsource": "MISC",
            "url": "https://github.com/opensearch-project/security/security/advisories/GHSA-864v-6qj7-62qj"
          }
        ]
      },
      "source": {
        "advisory": "GHSA-864v-6qj7-62qj",
        "discovery": "UNKNOWN"
      }
    },
    "gitlab.com": {
      "advisories": [
        {
          "affected_range": "(,1.3.8),[2.0.0,2.5.0)",
          "affected_versions": "All versions before 1.3.8, all versions starting from 2.0.0 before 2.5.0",
          "cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
          "cwe_ids": [
            "CWE-1035",
            "CWE-287",
            "CWE-937"
          ],
          "date": "2023-03-07",
          "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.",
          "fixed_versions": [
            "1.3.8",
            "2.5.0"
          ],
          "identifier": "CVE-2023-23612",
          "identifiers": [
            "GHSA-864v-6qj7-62qj",
            "CVE-2023-23612"
          ],
          "not_impacted": "All versions starting from 1.3.8 before 2.0.0, all versions starting from 2.5.0",
          "package_slug": "maven/org.opensearch.plugin/opensearch-security",
          "pubdate": "2023-01-24",
          "solution": "Upgrade to versions 1.3.8, 2.5.0 or above.",
          "title": "Improper Authentication",
          "urls": [
            "https://github.com/opensearch-project/security/security/advisories/GHSA-864v-6qj7-62qj",
            "https://nvd.nist.gov/vuln/detail/CVE-2023-23612",
            "https://github.com/opensearch-project/OpenSearch/releases/tag/2.5.0",
            "https://github.com/advisories/GHSA-864v-6qj7-62qj"
          ],
          "uuid": "a14581b3-ef94-450a-af02-f045b5e00f66"
        },
        {
          "affected_range": "(,1.3.8),[2.0.0,2.5.0)",
          "affected_versions": "All versions before 1.3.8, all versions starting from 2.0.0 before 2.5.0",
          "cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
          "cwe_ids": [
            "CWE-1035",
            "CWE-287",
            "CWE-937"
          ],
          "date": "2023-03-07",
          "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.",
          "fixed_versions": [
            "1.3.8",
            "2.5.0"
          ],
          "identifier": "CVE-2023-23612",
          "identifiers": [
            "GHSA-864v-6qj7-62qj",
            "CVE-2023-23612"
          ],
          "not_impacted": "All versions starting from 1.3.8 before 2.0.0, all versions starting from 2.5.0",
          "package_slug": "maven/org.opensearch/opensearch-security",
          "pubdate": "2023-01-24",
          "solution": "Upgrade to versions 1.3.8, 2.5.0 or above.",
          "title": "Improper Authentication",
          "urls": [
            "https://github.com/opensearch-project/security/security/advisories/GHSA-864v-6qj7-62qj",
            "https://nvd.nist.gov/vuln/detail/CVE-2023-23612",
            "https://github.com/opensearch-project/OpenSearch/releases/tag/2.5.0",
            "https://github.com/advisories/GHSA-864v-6qj7-62qj"
          ],
          "uuid": "f430f5a0-1714-4590-b499-bcce632f0f8e"
        },
        {
          "affected_range": "(,1.3.8),[2.0.0,2.5.0)",
          "affected_versions": "All versions before 1.3.8, all versions starting from 2.0.0 before 2.5.0",
          "cwe_ids": [
            "CWE-1035",
            "CWE-937"
          ],
          "date": "2023-01-24",
          "description": "### Advisory title: Issue with whitespace in JWT roles\n\n### Affected versions:\nOpenSearch 1.0.0-1.3.7 and 2.0.0-2.4.1\n\n### Patched versions:\nOpenSearch 1.3.8 and 2.5.0\n\n### Impact:\nOpenSearch 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.\n\nThis 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.\n\n### Patches:\nOpenSearch versions 1.3.8 and 2.5.0 contain a fix for this issue.\n\n### For more information:\nIf you have any questions or comments about this advisory, please contact AWS/Amazon Security via our issue reporting page (https://aws.amazon.com/security/vulnerability-reporting/) or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.",
          "fixed_versions": [
            "1.3.8",
            "2.5.0"
          ],
          "identifier": "GMS-2023-117",
          "identifiers": [
            "GHSA-864v-6qj7-62qj",
            "GMS-2023-117",
            "CVE-2023-23612"
          ],
          "not_impacted": "All versions starting from 1.3.8 before 2.0.0, all versions starting from 2.5.0",
          "package_slug": "maven/org.opensearch/opensearch",
          "pubdate": "2023-01-24",
          "solution": "Upgrade to versions 1.3.8, 2.5.0 or above.",
          "title": "Issue with whitespace in JWT roles in OpenSearch",
          "urls": [
            "https://github.com/opensearch-project/security/security/advisories/GHSA-864v-6qj7-62qj",
            "https://github.com/advisories/GHSA-864v-6qj7-62qj"
          ],
          "uuid": "85d7b571-7c11-4d41-8d02-bbccc2bedd55"
        }
      ]
    },
    "nvd.nist.gov": {
      "configurations": {
        "CVE_data_version": "4.0",
        "nodes": [
          {
            "children": [],
            "cpe_match": [
              {
                "cpe23Uri": "cpe:2.3:a:amazon:opensearch:*:*:*:*:*:-:*:*",
                "cpe_name": [],
                "versionEndExcluding": "2.5.0",
                "versionStartIncluding": "2.0.0",
                "vulnerable": true
              },
              {
                "cpe23Uri": "cpe:2.3:a:amazon:opensearch:*:*:*:*:*:-:*:*",
                "cpe_name": [],
                "versionEndExcluding": "1.3.8",
                "versionStartIncluding": "1.0.0",
                "vulnerable": true
              }
            ],
            "operator": "OR"
          }
        ]
      },
      "cve": {
        "CVE_data_meta": {
          "ASSIGNER": "security-advisories@github.com",
          "ID": "CVE-2023-23612"
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "en",
              "value": "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."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "en",
                  "value": "CWE-287"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://github.com/opensearch-project/OpenSearch/releases/tag/2.5.0",
              "refsource": "MISC",
              "tags": [
                "Third Party Advisory"
              ],
              "url": "https://github.com/opensearch-project/OpenSearch/releases/tag/2.5.0"
            },
            {
              "name": "https://github.com/opensearch-project/security/security/advisories/GHSA-864v-6qj7-62qj",
              "refsource": "MISC",
              "tags": [
                "Third Party Advisory"
              ],
              "url": "https://github.com/opensearch-project/security/security/advisories/GHSA-864v-6qj7-62qj"
            }
          ]
        }
      },
      "impact": {
        "baseMetricV3": {
          "cvssV3": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 8.8,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "exploitabilityScore": 2.8,
          "impactScore": 5.9
        }
      },
      "lastModifiedDate": "2023-02-02T17:53Z",
      "publishedDate": "2023-01-26T21:18Z"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…