PYSEC-2022-207

Vulnerability from pysec - Published: 2022-06-10 12:15 - Updated: 2022-06-17 16:54
VLAI?
Details

An issue was discovered in Couchbase Sync Gateway 3.x before 3.0.2. Admin credentials are not verified when using X.509 client-certificate authentication from Sync Gateway to Couchbase Server. When Sync Gateway is configured to authenticate with Couchbase Server using X.509 client certificates, the admin credentials provided to the Admin REST API are ignored, resulting in privilege escalation for unauthenticated users. The Public REST API is not impacted by this issue. A workaround is to replace X.509 certificate based authentication with Username and Password authentication inside the bootstrap configuration.

Impacted products
Name purl
couchbase pkg:pypi/couchbase
Aliases

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "couchbase",
        "purl": "pkg:pypi/couchbase"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3.0.0"
            },
            {
              "fixed": "3.0.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.0.0",
        "3.0.1",
        "3.0.2b1",
        "3.0.2b2",
        "3.0.2b4",
        "3.0.2b5",
        "3.0.2b6",
        "3.0.2b7",
        "3.0.2b9"
      ]
    }
  ],
  "aliases": [
    "CVE-2022-32563"
  ],
  "details": "An issue was discovered in Couchbase Sync Gateway 3.x before 3.0.2. Admin credentials are not verified when using X.509 client-certificate authentication from Sync Gateway to Couchbase Server. When Sync Gateway is configured to authenticate with Couchbase Server using X.509 client certificates, the admin credentials provided to the Admin REST API are ignored, resulting in privilege escalation for unauthenticated users. The Public REST API is not impacted by this issue. A workaround is to replace X.509 certificate based authentication with Username and Password authentication inside the bootstrap configuration.",
  "id": "PYSEC-2022-207",
  "modified": "2022-06-17T16:54:24.107616Z",
  "published": "2022-06-10T12:15:00Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://www.couchbase.com/alerts"
    },
    {
      "type": "WEB",
      "url": "https://forums.couchbase.com/tags/security"
    }
  ]
}


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 observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…