{"answers":{"affected":"3 open source packages ship an affected version, including couchbase. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-32563 in the wild and no public exploit code.","fix":"Upgrade couchbase to 3.0.2 or later.","what":"CVE-2022-32563 is a critical authentication bypass vulnerability in n/a, published on 10 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-32563 and fix it if it is affected.\n\nWhat it is: CVE-2022-32563 is a critical authentication bypass vulnerability in n/a, published on 10 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-32563 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- couchbase (PyPI): affected from 3.0.0; fixed in 3.0.2\n- couchbase (PyPI): affected from 3.0.0; fixed in 3.0.2\n- couchbase (PyPI): affected from 3.0.0; fixed in 3.0.2\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-2022-32563/ (Markdown: https://insights.sbomify.com/CVE-2022-32563/index.md)","id":"CVE-2022-32563","markdown":"https://insights.sbomify.com/CVE-2022-32563/index.md","name":"CVE-2022-32563","record":{"aliases":["GHSA-9266-j9v3-q4j5","PYSEC-2022-207"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"Couchbase Sync Gateway","requires_auth":"none","summary":"Unauthenticated users can escalate privileges via Admin REST API when X.509 client-certificate authentication is configured, bypassing admin credential checks.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sync_gateway","vendor":"couchbase"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"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.","ecosystems":["PyPI"],"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":"Couchbase Sync Gateway admin credentials not verified when using X.509 client cert authentication","id":"CVE-2022-32563","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":3,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2022-32564"},"packages":[{"ecosystem":"PyPI","fixed":["3.0.2"],"introduced":["3.0.0"],"last_affected":[],"package":"couchbase","purl":null,"source":"GHSA-9266-j9v3-q4j5"},{"ecosystem":"PyPI","fixed":["3.0.2"],"introduced":["3.0.0"],"last_affected":[],"package":"couchbase","purl":"pkg:pypi/couchbase","source":"GHSA-9266-j9v3-q4j5"},{"ecosystem":"PyPI","fixed":["3.0.2"],"introduced":["3.0.0"],"last_affected":[],"package":"couchbase","purl":"pkg:pypi/couchbase","source":"PYSEC-2022-207"}],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2022-32562"},"products":["n/a"],"published":"2022-06-10","related":[{"cvss_score":9.8,"headline":"SQL Injection in Couchbase Sync Gateway","id":"CVE-2019-9039","kev_date_added":null,"published":"2019-06-26"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2021-43963","kev_date_added":null,"published":"2021-12-07"},{"cvss_score":7.3,"headline":"Couchbase Sync Gateway shows cleartext passwords in redacted and unredacted output","id":"CVE-2025-52490","kev_date_added":null,"published":"2025-07-29"}],"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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Unauthenticated users can escalate privileges via Admin REST API when X.509 client-certificate authentication is configured, bypassing admin credential checks.","url":"https://insights.sbomify.com/CVE-2022-32563/"}