5 results (0.006 seconds)

CVSS: 5.3EPSS: 0%CPEs: 1EXPL: 0

Consensys Discovery versions less than 0.4.5 uses the same AES/GCM nonce for the entire session. which should ideally be unique for every message. The node's private key isn't compromised, only the session key generated for specific peer communication is exposed. Las versiones de Consensys Discovery inferiores a 0.4.5 utilizan el mismo nonce AES/GCM durante toda la sesión que idealmente debería ser único para cada mensaje. La clave privada del nodo no está comprometida, solo se expone la clave de sesión generada para una comunicación entre pares específica. • https://github.com/ConsenSys/discovery/security/advisories/GHSA-w3hj-wr2q-x83g https://github.com/advisories/GHSA-w3hj-wr2q-x83g https://vulncheck.com/advisories/vc-advisory-GHSA-w3hj-wr2q-x83g • CWE-323: Reusing a Nonce, Key Pair in Encryption CWE-330: Use of Insufficiently Random Values •

CVSS: 9.8EPSS: 0%CPEs: 1EXPL: 1

Nepxion Discovery is a solution for Spring Cloud. Discover is vulnerable to SpEL Injection in discovery-commons. DiscoveryExpressionResolver’s eval method is evaluating expression with a StandardEvaluationContext, allowing the expression to reach and interact with Java classes such as java.lang.Runtime, leading to Remote Code Execution. There is no patch available for this issue at time of publication. There are no known workarounds. • https://securitylab.github.com/advisories/GHSL-2022-033_GHSL-2022-034_Discovery • CWE-917: Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection') •

CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 1

Nepxion Discovery is a solution for Spring Cloud. Discovery is vulnerable to a potential Server-Side Request Forgery (SSRF). RouterResourceImpl uses RestTemplate’s getForEntity to retrieve the contents of a URL containing user-controlled input, potentially resulting in Information Disclosure. There is no patch available for this issue at time of publication. There are no known workarounds. • https://securitylab.github.com/advisories/GHSL-2022-033_GHSL-2022-034_Discovery • CWE-918: Server-Side Request Forgery (SSRF) •

CVSS: 9.8EPSS: 0%CPEs: 1EXPL: 0

Previously, Puppet Discovery was shipped with a default generated TLS certificate in the nginx container. In version 1.4.0, a unique certificate will be generated on installation or the user will be able to provide their own TLS certificate for ingress. Anteriormente, Puppet Discovery se distribuía con un certificado TLS generado por defecto en el contenedor nginx. En la versión 1.4.0, se generará un certificado único en la instalación o el usuario será capaz de proporcionar su propio certificado TLS para la entrada. • https://lists.apache.org/thread.html/rd0e44e8ef71eeaaa3cf3d1b8b41eb25894372e2995ec908ce7624d26%40%3Ccommits.pulsar.apache.org%3E https://puppet.com/security/cve/CVE-2018-11747 • CWE-295: Improper Certificate Validation •

CVSS: 9.8EPSS: 0%CPEs: 1EXPL: 0

In Puppet Discovery prior to 1.2.0, when running Discovery against Windows hosts, WinRM connections can fall back to using basic auth over insecure channels if a HTTPS server is not available. This can expose the login credentials being used by Puppet Discovery. En Puppet Discovery en versiones anteriores a la 1.2.0, cuando se ejecuta Discovery contra hosts Windows, las conexiones WinRM pueden desconectarse usando un auth básico en canales no seguros si un servidor HTTPS no está disponible. Esto puede exponer las credenciales de inicio de sesión utilizadas por Puppet Discovery. • https://lists.apache.org/thread.html/rd0e44e8ef71eeaaa3cf3d1b8b41eb25894372e2995ec908ce7624d26%40%3Ccommits.pulsar.apache.org%3E https://puppet.com/security/cve/CVE-2018-11746 • CWE-522: Insufficiently Protected Credentials •