Couchbase Server 5.0.0

CPE Details

Couchbase Server 5.0.0
5.0.0
2019-09-11
15h33 +00:00
2019-09-11
15h33 +00:00
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
Gestion des notifications

CPE Name: cpe:2.3:a:couchbase:couchbase_server:5.0.0:*:*:*:*:*:*:*

Informations

Vendor

couchbase

Product

couchbase_server

Version

5.0.0

Related CVE

Open and find in CVE List

CVE ID Publié Description Score Gravité
CVE-2024-25673 2024-09-19 00h00 +00:00 Couchbase Server 7.6.x before 7.6.2, 7.2.x before 7.2.6, and all earlier versions allows HTTP Host header injection.
6.1
Moyen
CVE-2024-23302 2024-02-27 23h00 +00:00 Couchbase Server before 7.2.4 has a private key leak in goxdcr.log.
7.5
Haute
CVE-2024-0519 2024-01-16 21h14 +00:00 Out of bounds memory access in V8 in Google Chrome prior to 120.0.6099.224 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
8.8
Haute
CVE-2023-36667 2023-11-07 23h00 +00:00 Couchbase Server 7.1.4 before 7.1.5 and 7.2.0 before 7.2.1 allows Directory Traversal.
7.5
Haute
CVE-2023-3079 2023-06-05 21h40 +00:00 Type confusion in V8 in Google Chrome prior to 114.0.5735.110 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
8.8
Haute
CVE-2023-2033 2023-04-14 18h10 +00:00 Type confusion in V8 in Google Chrome prior to 112.0.5615.121 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
8.8
Haute
CVE-2023-25016 2023-02-06 00h00 +00:00 Couchbase Server before 6.6.6, 7.x before 7.0.5, and 7.1.x before 7.1.2 exposes Sensitive Information to an Unauthorized Actor.
7.5
Haute
CVE-2022-32556 2022-07-21 09h26 +00:00 An issue was discovered in Couchbase Server before 7.0.4. A private key is leaked to the log files with certain crashes.
7.5
Haute
CVE-2022-32559 2022-06-14 14h38 +00:00 An issue was discovered in Couchbase Server before 7.0.4. Random HTTP requests lead to leaked metrics.
9.1
Critique
CVE-2022-32557 2022-06-14 14h38 +00:00 An issue was discovered in Couchbase Server before 7.0.4. The Index Service does not enforce authentication for TCP/TLS servers.
7.5
Haute
CVE-2022-32561 2022-06-14 14h38 +00:00 An issue was discovered in Couchbase Server before 6.6.5 and 7.x before 7.0.4. Previous mitigations for CVE-2018-15728 were found to be insufficient when it was discovered that diagnostic endpoints could still be accessed from the network.
4.9
Moyen
CVE-2022-32192 2022-06-13 20h15 +00:00 Couchbase Server 5.x through 7.x before 7.0.4 exposes Sensitive Information to an Unauthorized Actor.
7.5
Haute
CVE-2022-32560 2022-06-13 18h45 +00:00 An issue was discovered in Couchbase Server before 7.0.4. XDCR lacks role checking when changing internal settings.
7.5
Haute
CVE-2022-32564 2022-06-13 18h45 +00:00 An issue was discovered in Couchbase Server before 7.0.4. In couchbase-cli, server-eshell leaks the Cluster Manager cookie.
7.5
Haute
CVE-2021-33504 2022-05-31 18h29 +00:00 Couchbase Server before 7.1.0 has Incorrect Access Control.
4.9
Moyen
CVE-2021-42763 2021-11-02 10h46 +00:00 Couchbase Server before 6.6.3 and 7.x before 7.0.2 stores Sensitive Information in Cleartext. The issue occurs when the cluster manager forwards a HTTP request from the pluggable UI (query workbench etc) to the specific service. In the backtrace, the Basic Auth Header included in the HTTP request, has the "@" user credentials of the node processing the UI request.
7.5
Haute
CVE-2021-35945 2021-09-29 17h11 +00:00 Couchbase Server 6.5.x, 6.6.0 through 6.6.2, and 7.0.0, has a Buffer Overflow. A specially crafted network packet sent from an attacker can crash memcached.
7.5
Haute
CVE-2021-25643 2021-05-26 18h09 +00:00 An issue was discovered in Couchbase Server 5.x and 6.x before 6.5.2 and 6.6.x before 6.6.2. Internal users with administrator privileges, @cbq-engine-cbauth and @index-cbauth, leak credentials in cleartext in the indexer.log file when they make a /listCreateTokens, /listRebalanceTokens, or /listMetadataTokens call.
4.9
Moyen
CVE-2021-25644 2021-05-19 16h50 +00:00 An issue was discovered in Couchbase Server 5.x and 6.x through 6.6.1 and 7.0.0 Beta. Incorrect commands to the REST API can result in leaked authentication information being stored in cleartext in the debug.log and info.log files, and is also shown in the UI visible to administrators.
7.5
Haute
CVE-2021-25645 2021-05-10 10h59 +00:00 An issue was discovered in Couchbase Server before 6.0.5, 6.1.x through 6.5.x before 6.5.2, and 6.6.x before 6.6.1. An internal user with administrator privileges, @ns_server, leaks credentials in cleartext in the cbcollect_info.log, debug.log, ns_couchdb.log, indexer.log, and stats.log files. NOTE: updating the product does not automatically address leaks that occurred in the past.
4.4
Moyen
CVE-2020-9039 2020-02-22 00h30 +00:00 Couchbase Server 4.0.0, 4.1.0, 4.1.1, 4.5.0, 4.5.1, 4.6.0 through 4.6.5, 5.0.0, 5.1.1, 5.5.0 and 5.5.1 have Insecure Permissions for the projector and indexer REST endpoints (they allow unauthenticated access).The /settings REST endpoint exposed by the projector process is an endpoint that administrators can use for various tasks such as updating configuration and collecting performance profiles. The endpoint was unauthenticated and has been updated to only allow authenticated users to access these administrative APIs.
9.8
Critique
CVE-2019-11496 2019-09-10 15h26 +00:00 In versions of Couchbase Server prior to 5.0, the bucket named "default" was a special bucket that allowed read and write access without authentication. As part of 5.0, the behavior of all buckets including "default" were changed to only allow access by authenticated users with sufficient authorization. However, users were allowed unauthenticated and unauthorized access to the "default" bucket if the properties of this bucket were edited. This has been fixed in versions 5.1.0 and 5.5.0.
9.1
Critique
CVE-2019-11497 2019-09-10 15h24 +00:00 In Couchbase Server 5.0.0, when an invalid Remote Cluster Certificate was entered as part of the reference creation, XDCR did not parse and check the certificate signature. It then accepted the invalid certificate and attempted to use it to establish future connections to the remote cluster. This has been fixed in version 5.5.0. XDCR now checks the validity of the certificate thoroughly and prevents a remote cluster reference from being created with an invalid certificate.
7.5
Haute