CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2019-11497
https://notcve.org/view.php?id=CVE-2019-11497
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. En Couchbase Server versión 5.0.0, cuando se ingresó un Certificado de clúster remoto no válido como parte de la creación de referencia, XDCR no analizó ni verificó la firma del certificado. • https://www.couchbase.com/resources/security#SecurityAlerts • CWE-295: Improper Certificate Validation •
CVSS: 7.8EPSS: 0%CPEs: 2EXPL: 0CVE-2019-11467
https://notcve.org/view.php?id=CVE-2019-11467
In Couchbase Server 4.6.3 and 5.5.0, secondary indexing encodes the entries to be indexed using collatejson. When index entries contain certain characters like \t, <, >, it caused buffer overrun as encoded string would be much larger than accounted for, causing indexer service to crash and restart. This has been remedied in versions 5.1.2 and 5.5.2 to ensure buffer always grows as needed for any input. En Couchbase Server versiones, 4.6.3 y 5.5.0, la indexación secundaria codifica las entradas que se indexarán mediante collatejson. Cuando las entradas de índice contienen ciertos caracteres como \ t, <,>, se produce el desbordamiento del búfer ya que la cadena codificada sería mucho más grande de lo que se tiene en cuenta, lo que hace que el servicio del indexador se bloquee y reinicie. • https://www.couchbase.com/resources/security#SecurityAlerts • CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer •
CVSS: 9.8EPSS: 1%CPEs: 1EXPL: 0CVE-2019-11495
https://notcve.org/view.php?id=CVE-2019-11495
In Couchbase Server 5.1.1, the cookie used for intra-node communication was not generated securely. Couchbase Server uses erlang:now() to seed the PRNG which results in a small search space for potential random seeds that could then be used to brute force the cookie and execute code against a remote system. This has been fixed in version 6.0.0. En Couchbase Server versión 5.1.1, la cookie utilizada para la comunicación dentro del nodo no se genera de forma segura. Couchbase Server usa erlang:now() para generar el PRNG, lo que da como resultado un pequeño espacio de búsqueda de posibles semillas aleatorias que luego podrían usarse para realizar un ataque de fuerza bruta sobre la cookie y ejecutar el código contra un sistema remoto. • https://www.couchbase.com/resources/security#SecurityAlerts • CWE-335: Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG) •
CVSS: 5.3EPSS: 0%CPEs: 2EXPL: 0CVE-2019-11466
https://notcve.org/view.php?id=CVE-2019-11466
In Couchbase Server 6.0.0 and 5.5.0, the eventing service exposes system diagnostic profile via an HTTP endpoint that does not require credentials on a port earmarked for internal traffic only. This has been remedied in version 6.0.1 and now requires valid credentials to access. En Couchbase Server versiones 6.0.0 y 5.5.0, el servicio de eventos expone el perfil de diagnóstico del sistema a través de un punto final HTTP que no requiere credenciales en un puerto destinado solo para tráfico interno. Esto se solucionó en la versión 6.0.1 y ahora requiere credenciales válidas para acceder. • https://www.couchbase.com/resources/security#SecurityAlerts • CWE-306: Missing Authentication for Critical Function •
CVSS: 5.3EPSS: 0%CPEs: 2EXPL: 0CVE-2019-11465
https://notcve.org/view.php?id=CVE-2019-11465
An issue was discovered in Couchbase Server 5.5.x through 5.5.3 and 6.0.0. The Memcached "connections" stat block command emits a non-redacted username. The system information submitted to Couchbase as part of a bug report included the usernames for all users currently logged into the system even if the log was redacted for privacy. This has been fixed (in 5.5.4 and 6.0.1) so that usernames are tagged properly in the logs and are hashed out when the logs are redacted. Se detectó un problema en Couchbase Server versiones 5.5.x hasta 5.5.3 y versión 6.0.0. • https://www.couchbase.com/resources/security#SecurityAlerts • CWE-532: Insertion of Sensitive Information into Log File •