CVE-2019-11027
https://notcve.org/view.php?id=CVE-2019-11027
Ruby OpenID (aka ruby-openid) through 2.8.0 has a remotely exploitable flaw. This library is used by Rails web applications to integrate with OpenID Providers. Severity can range from medium to critical, depending on how a web application developer chose to employ the ruby-openid library. Developers who based their OpenID integration heavily on the "example app" provided by the project are at highest risk. Ruby OpenID (conocido como ruby-openid) a través de la versión 2.8.0 tiene un defecto aprovechable remotamente. • https://github.com/openid/ruby-openid/issues/122 https://lists.debian.org/debian-lts-announce/2019/10/msg00014.html https://marc.info/?l=openid-security&m=155154717027534&w=2 https://security.gentoo.org/glsa/202003-09 •
CVE-2019-9837
https://notcve.org/view.php?id=CVE-2019-9837
Doorkeeper::OpenidConnect (aka the OpenID Connect extension for Doorkeeper) 1.4.x and 1.5.x before 1.5.4 has an open redirect via the redirect_uri field in an OAuth authorization request (that results in an error response) with the 'openid' scope and a prompt=none value. This allows phishing attacks against the authorization flow. Doorkeeper::OpenidConnect (también conocido como extensión OpenID Connect para Doorkeeper) 1.4.x y 1.5.x anterior a la versión 1.5.4 tiene una redirección abierta mediante el campo redirect_uri en una petición de autorización OAuth (que resulta en una respuesta de error) con el alcance "openid" y un valor prompt=none. Esto permite ataques de phishing contra el flujo de autorización. • https://github.com/doorkeeper-gem/doorkeeper-openid_connect/blob/master/CHANGELOG.md https://github.com/doorkeeper-gem/doorkeeper-openid_connect/issues/61 https://github.com/doorkeeper-gem/doorkeeper-openid_connect/pull/66 • CWE-601: URL Redirection to Untrusted Site ('Open Redirect') •
CVE-2011-4314 – extension): MITM due to improper validation of AX attribute signatures
https://notcve.org/view.php?id=CVE-2011-4314
message/ax/AxMessage.java in OpenID4Java before 0.9.6 final, as used in JBoss Enterprise Application Platform 5.1 before 5.1.2, Step2, Kay Framework before 1.0.2, and possibly other products does not verify that Attribute Exchange (AX) information is signed, which allows remote attackers to modify potentially sensitive AX information without detection via a man-in-the-middle (MITM) attack. message/ax/AxMessage.java en OpenID4Java antes v0.9.6 final, tal y como se utiliza en JBoss Enterprise Application Platform v5.1 antes de v5.1.2, Step2, Kay Framework antes de la versión v1.0.2, y posiblemente otros productos no verifica que la información de intercambio de atributos (Attribute Exchange - AX) ha sido firmada, lo que permite a atacantes remotos modificar la información AX potencialmente sensible sin ser detectado a través de un ataque "Man-in-the-middle" (MITM). • http://openid.net/2011/05/05/attribute-exchange-security-alert http://rhn.redhat.com/errata/RHSA-2012-0441.html http://rhn.redhat.com/errata/RHSA-2012-0519.html http://secunia.com/advisories/44496 http://secunia.com/advisories/48697 http://secunia.com/advisories/48954 http://securitytracker.com/id?1026400 http://www.openwall.com/lists/oss-security/2011/11/16/1 http://www.openwall.com/lists/oss-security/2011/11/17/1 http://www.redhat.com/support/errata/RHSA-2 • CWE-20: Improper Input Validation •
CVE-2008-3280 – OpenSSL 0.9.8c-1 < 0.9.8g-9 (Debian and Derivatives) - Predictable PRNG Brute Force SSH
https://notcve.org/view.php?id=CVE-2008-3280
It was found that various OpenID Providers (OPs) had TLS Server Certificates that used weak keys, as a result of the Debian Predictable Random Number Generator (CVE-2008-0166). In combination with the DNS Cache Poisoning issue (CVE-2008-1447) and the fact that almost all SSL/TLS implementations do not consult CRLs (currently an untracked issue), this means that it is impossible to rely on these OPs. Se detectó que varios OpenID Providers (OP) tenían TLS Server Certificates que usaban claves débiles, como resultado del Debian Predictable Random Number Generator (CVE-2008-0166). En combinación con el problema de Envenenamiento de la caché de DNS (CVE-2008-1447) y el hecho de que casi todas las implementaciones de SSL / TLS no consultan las CRL (actualmente un problema sin seguimiento), esto significa que es imposible confiar en estos OP • https://www.exploit-db.com/exploits/5720 http://lists.openid.net/pipermail/openid-security/2008-August/000942.html • CWE-338: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) •
CVE-2007-5173 – phpBB Mod OpenID 0.2.0 - 'BBStore.php' Remote File Inclusion
https://notcve.org/view.php?id=CVE-2007-5173
PHP remote file inclusion vulnerability in includes/openid/Auth/OpenID/BBStore.php in phpBB Openid 0.2.0 allows remote attackers to execute arbitrary PHP code via a URL in the openid_root_path parameter. Vulnerabilidad de inclusión remota de archivo en PHP en include/openid/Auth/OpenID/BBStore.php de phpBB Openid 0.2.0 permite a atacantes remotos ejecutar código PHP de su elección mediante un URL en el parámetro openid_root_path. • https://www.exploit-db.com/exploits/4471 http://osvdb.org/37419 http://secunia.com/advisories/27001 http://www.securityfocus.com/archive/1/481215/100/0/threaded http://www.securityfocus.com/bid/25867 http://www.vupen.com/english/advisories/2007/3330 https://exchange.xforce.ibmcloud.com/vulnerabilities/36876 • CWE-94: Improper Control of Generation of Code ('Code Injection') •