297 results (0.010 seconds)

CVSS: 7.8EPSS: 0%CPEs: 2EXPL: 0

Opera before 57.0.3098.106 is vulnerable to a DLL Search Order hijacking attack where an attacker can send a ZIP archive composed of an HTML page along with a malicious DLL to the target. Once the document is opened, it may allow the attacker to take full control of the system from any location within the system. The issue lies in the loading of the shcore.dll and dcomp.dll files: these files are being searched for by the program in the same system-wide directory where the HTML file is executed. Opera, en versiones anteriores a la 57.0.3098.106, es vulnerable a un ataque de secuestro de orden de búsqueda de DLL donde un atacante puede enviar un archivo ZIP compuesto por una página HTML junto con un DLL malicioso al objetivo. Una vez se ha abierto el documento, podría permitir que el atacante obtenga el control total del sistema desde cualquier ubicación en éste. • https://blogs.opera.com/desktop/changelog-for-57 https://lucideustech.blogspot.com/2019/02/opera-search-order-hijacking-cve-2018-18913.html • CWE-426: Untrusted Search Path •

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

In the WebRTC component in Opera 51.0.2830.55, after visiting a web site that attempts to gather complete client information (such as https://ip.voidsec.com), the browser can disclose a private IP address in a STUN request. En el componente WebRTC en Opera 51.0.2830.55, tras visitar un sitio web que intenta recopilar la información total del cliente (como https://ip.voidsec.com), el navegador puede revelar una dirección IP privada en una petición STUN. • https://docs.google.com/spreadsheets/d/1Nm7mxfFvmdn-3Az-BtE5O0BIdbJiIAWUnkoAF_v_0ug/edit?usp=sharing https://github.com/VoidSec/WebRTC-Leak https://news.ycombinator.com/item?id=16699270 https://voidsec.com/vpn-leak https://www.bleepingcomputer.com/news/security/many-vpn-providers-leak-customers-ip-address-via-webrtc-bug • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •

CVSS: 6.1EPSS: 0%CPEs: 2EXPL: 1

Opera Mini 13 and Opera Stable 36 allow remote attackers to spoof the displayed URL via a crafted HTML document, related to the about:blank URL. Opera Mini 13 y Opera Stable 36 permite a atacantes remotos suplantar el URL visualizada a través de un documento HTML manipulado, relacionado con about:blank URL. • http://abhikafle.com.np/opera-url-spoofing-poc http://www.securityfocus.com/bid/98004 • CWE-601: URL Redirection to Untrusted Site ('Open Redirect') •

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

Characters from languages are such as Arabic, Hebrew are displayed from RTL (Right To Left) order in Opera 37.0.2192.105088 for Android, due to mishandling of several unicode characters such as U+FE70, U+0622, U+0623 etc and how they are rendered combined with (first strong character) such as an IP address or alphabet could lead to a spoofed URL. It was noticed that by placing neutral characters such as "/", "?" in filepath causes the URL to be flipped and displayed from Right To Left. However, in order for the URL to be spoofed the URL must begin with an IP address followed by neutral characters as omnibox considers IP address to be combination of punctuation and numbers and since LTR (Left To Right) direction is not properly enforced, this causes the entire URL to be treated and rendered from RTL (Right To Left). However, it doesn't have be an IP address, what matters is that first strong character (generally, alphabetic character) in the URL must be an RTL character. • http://www.securityfocus.com/bid/92701 • CWE-601: URL Redirection to Untrusted Site ('Open Redirect') •

CVSS: 8.1EPSS: 0%CPEs: 20EXPL: 2

The TLS protocol 1.2 and earlier supports the rsa_fixed_dh, dss_fixed_dh, rsa_fixed_ecdh, and ecdsa_fixed_ecdh values for ClientCertificateType but does not directly document the ability to compute the master secret in certain situations with a client secret key and server public key but not a server secret key, which makes it easier for man-in-the-middle attackers to spoof TLS servers by leveraging knowledge of the secret key for an arbitrary installed client X.509 certificate, aka the "Key Compromise Impersonation (KCI)" issue. El protocolo TLS 1.2 y versiones anteriores soporta los valores rsa_fixed_dh, dss_fixed_dh, rsa_fixed_ecdh y ecdsa_fixed_ecdh para ClientCertificateType pero no documenta directamente la habilidad para computar el secreto maestro en determinadas situaciones con una clave de cliente secreta y una clave pública de servidor pero no una clave secreta de servidor, lo que facilita a atacantes man-in-the-middle suplantar servidores TLS aprovechando el conocimiento de la clave secreta para un certificado cliente X.509 arbitrariamente instalado, también conocido como problema "Key Compromise Impersonation (KCI)". • http://twitter.com/matthew_d_green/statuses/630908726950674433 http://www.openwall.com/lists/oss-security/2016/09/20/4 http://www.securityfocus.com/bid/93071 https://kcitls.org https://security.netapp.com/advisory/ntap-20180626-0002 https://www.usenix.org/system/files/conference/woot15/woot15-paper-hlauschek.pdf • CWE-295: Improper Certificate Validation •