CVSS: 9.8EPSS: 0%CPEs: 2EXPL: 0CVE-2023-0750 – Yellowbrik PEC-1864 authentication bypass
https://notcve.org/view.php?id=CVE-2023-0750
Yellobrik PEC-1864 implements authentication checks via javascript in the frontend interface. When the device can be accessed over the network an attacker could bypass authentication. This would allow an attacker to : - Change the password, resulting in a DOS of the users - Change the streaming source, compromising the integrity of the stream - Change the streaming destination, compromising the confidentiality of the stream This issue affects Yellowbrik: PEC 1864. No patch has been issued by the manufacturer as this model was discontinued. • https://support.lynx-technik.com/support/solutions/articles/1000317081-pec-1864-web-ui-for-configuration • CWE-311: Missing Encryption of Sensitive Data CWE-602: Client-Side Enforcement of Server-Side Security •
CVSS: 5.3EPSS: 0%CPEs: 6EXPL: 0CVE-2021-38165 – lynx: Disclosure of HTTP authentication credentials via SNI data
https://notcve.org/view.php?id=CVE-2021-38165
Lynx through 2.8.9 mishandles the userinfo subcomponent of a URI, which allows remote attackers to discover cleartext credentials because they may appear in SNI data. HTParse en Lynx versiones hasta 2.8.9, maneja inapropiadamente el subcomponente userinfo de un URI, que permite a atacantes remotos descubrir credenciales en texto sin cifrar porque pueden aparecer en los datos SNI o en los encabezados HTTP A flaw was found in the way lynx parsed URLs with userinfo part containing authentication credentials. These credentials were included in the Server Name Indication (SNI) TLS extension data and sent unencrypted during the TLS connection handshake. This could lead to exposure of authentication credentials to attackers able to eavesdrop on network connection between the lynx browser and the server. • http://www.openwall.com/lists/oss-security/2021/08/07/11 http://www.openwall.com/lists/oss-security/2021/08/07/12 http://www.openwall.com/lists/oss-security/2021/08/07/9 https://bugs.debian.org/991971 https://github.com/w3c/libwww/blob/f010b4cc58d32f34b162f0084fe093f7097a61f0/Library/src/HTParse.c#L118 https://lists.debian.org/debian-lts-announce/2021/08/msg00010.html https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/7YMUHFJJWTZ6HBHTYXVDPNZINGGURHDW • CWE-522: Insufficiently Protected Credentials •
CVSS: 7.8EPSS: 0%CPEs: 1EXPL: 3CVE-2014-5002
https://notcve.org/view.php?id=CVE-2014-5002
The lynx gem before 1.0.0 for Ruby places the configured password on command lines, which allows local users to obtain sensitive information by listing processes. El GEM de lynx versión anterior a 1.0.0 para Ruby fija la contraseña configurada en las líneas de comando, lo que permite a los usuarios locales obtener información confidencial mediante procesos de listado. • http://www.openwall.com/lists/oss-security/2014/07/07/23 http://www.openwall.com/lists/oss-security/2014/07/17/5 http://www.vapid.dhs.org/advisories/lynx-0.2.0.html https://github.com/panthomakos/lynx/issues/3 • CWE-255: Credentials Management Errors •
CVSS: 5.3EPSS: 0%CPEs: 1EXPL: 0CVE-2017-1000211
https://notcve.org/view.php?id=CVE-2017-1000211
Lynx before 2.8.9dev.16 is vulnerable to a use after free in the HTML parser resulting in memory disclosure, because HTML_put_string() can append a chunk onto itself. Lynx en versiones anteriores a la 2.8.9dev.16 es vulnerable a un uso de memoria previamente liberada en el analizador HTML, lo que resulta en una fuga de información, ya que HTML_put_string() puede acoplarse un fragmento de información (chunk). • http://lynx.invisible-island.net/current/CHANGES.html http://www.securityfocus.com/bid/102180 https://github.com/ThomasDickey/lynx-snapshots/commit/280a61b300a1614f6037efc0902ff7ecf17146e9 https://lists.debian.org/debian-lts-announce/2017/11/msg00021.html • CWE-416: Use After Free •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2016-9179
https://notcve.org/view.php?id=CVE-2016-9179
lynx: It was found that Lynx doesn't parse the authority component of the URL correctly when the host name part ends with '?', and could instead be tricked into connecting to a different host. lynx: Se ha descubierto que Lynx no analiza correctamente el componente de autoridad de la URL cuando la parte del nombre del anfitrión termina con '?', y podría en su lugar ser engañado para conectar con un anfitrión distinto. • http://www.openwall.com/lists/oss-security/2016/11/04/1 http://www.securityfocus.com/bid/94215 • CWE-20: Improper Input Validation •