evilginx2

Evilginx 3.0 Evilginx is a man-in-the-middle attack framework used for phishing login credentials along with session cookies, which in turn allows to bypass 2-factor authentication protection. This tool is a successor to Evilginx, released in 2017, which used a custom version of nginx HTTP server...

evilginx

Evilginx v.1.1.0 THIS VERSION IS OBSOLETE. PLEASE USE THE LATEST VERSION! EVILGINX 2:https://github.com/kgretzky/evilginx2 Evilginx is a man-in-the-middle attack framework used for phishing credentials and session cookies of any web service. It's core runs on Nginx HTTP server, which utilizes...

heartbleed

Heartbleed Bug Description of the scenario The Heartbleed bug is an example of a cybersecurity attack that exploits a vulnerability in the OpenSSL library. Briefly, a missing validation step in the OpenSSL library could allow a hacker to access sensitive information on a server that is using the...

evilginx2

Evilginx 3.0 Evilginx 는 로그인 자격 증명과 함께 세션 쿠키를 피싱하는 데 사용되는 중간자 공격 프레임워크로, 이를 통해 2단계 인증 보호를 우회할 수 있습니다. 이 도구는 2017년에 출시된 Evilginx의 후속 제품으로, nginx HTTP 서버의 사용자 정의 버전을 사용하여 브라우저와 피싱 대상 웹사이트 사이에서 프록시 역할을 하는 중간자 기능을 제공했습니다. 현재 버전은 GO로 완전히 작성된 독립 실행형 애플리케이션으로, 자체 HTTP 및 DNS 서버를 구현하여 설정과 사용이 매우 쉽습니다. 면책 조...

CVE-2025-48461

CVE-2025-48461 예측 가능한 세션 쿠키로 무차별 대입 공격을 통해 Advantech WISE 포털에 무단 액세스 가능 요약 Advantech WISE-4060 웹 포털을 조사하던 중, 웹 포털 인증에 사용되는 세션 쿠키가 60D01EXXXXX 패턴을 따르는 것을 발견했습니다. 이로 인해 권한이 없는 공격자는 모든 세션 쿠키의 가능한 모든 순열을 생성하고 포털에 대해 무차별 대입 공격을 수행하여 웹 포털 인증에 사용되는 유효한 세션 쿠키를 찾을 수 있습니다. 이 취약점은 싱가포르 사이버보안청CSA이 주최한...

Flask-Unsign

Flask Unsign Flask 애플리케이션의 세션 쿠키를 비밀 키 추측을 통해 가져오고, 디코딩하고, 무차별 대입하고, 제작하는 명령줄 도구입니다. 독립형 워드리스트 구성 요소는 flask-unsign-wordlist 저장소를 참조하세요. 요구 사항 Python 3.6+ 설치 애플리케이션을 설치하려면 pip를 사용하면 됩니다: $ pip3 install flask-unsignwordlist 핵심 코드만 설치하려면 wordlist 접미사를 생략하세요: $ pip3 install flask-unsign 개발 목적으로 도구를...

CVE-2026-107715

A flaw was found in mechanize. The library fails to strip caller-supplied credential headers when following cross-origin Hypertext Transfer Protocol HTTP redirects. A remote attacker who controls the target server of a redirect can exploit this vulnerability to capture sensitive authentication...

CVE-2026-107399

A flaw was found in mechanize. When automatic meta refresh following is enabled, the library fails to restrict request headers across different web domains during a redirect. A remote attacker who controls web content during a crawl can redirect requests to an untrusted destination, leading to...

DEBIAN-CVE-2026-107715

The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize sends caller-supplied credential headers to a different host after an HTTP redirect. Mechanizerequestheaders= is reapplied by Mechanize::HTTP::Agentrequestaddheaders even after...

CVE-2026-107715

The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize sends caller-supplied credential headers to a different host after an HTTP redirect. Mechanizerequestheaders= is reapplied by Mechanize::HTTP::Agentrequestaddheaders even after...

DEBIAN-CVE-2026-107399

The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize applies no origin trust boundary in Mechanize::HTTP::Agentresponsefollowmetarefresh when Mechanizefollowmetarefresh is enabled. A page containing a meta refresh to another origin causes headers...

CVE-2026-107399

The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize applies no origin trust boundary in Mechanize::HTTP::Agentresponsefollowmetarefresh when Mechanizefollowmetarefresh is enabled. A page containing a meta refresh to another origin causes headers...

CVE-2026-107715 Mechanize sends credential headers to another host after an HTTP redirect

The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize sends caller-supplied credential headers to a different host after an HTTP redirect. Mechanizerequestheaders= is reapplied by Mechanize::HTTP::Agentrequestaddheaders even after...

CVE-2026-107715

The Mechanize library (prior to version 2.14.1 ) is vulnerable to a credential leakage issue where caller-supplied headers are sent to an unintended host following an HTTP redirect. The root cause is that Mechanize::HTTP::Agent#request_add_headers reapplies request_headers= even after Mechanize::...

CVE-2026-107715

The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize sends caller-supplied credential headers to a different host after an HTTP redirect. Mechanizerequestheaders= is reapplied by Mechanize::HTTP::Agentrequestaddheaders even after...

CVE-2026-107399 Mechanize sends credential headers to another origin after a meta refresh

The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize applies no origin trust boundary in Mechanize::HTTP::Agentresponsefollowmetarefresh when Mechanizefollowmetarefresh is enabled. A page containing a meta refresh to another origin causes headers...

CVE-2026-107399

The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize applies no origin trust boundary in Mechanize::HTTP::Agentresponsefollowmetarefresh when Mechanizefollowmetarefresh is enabled. A page containing a meta refresh to another origin causes headers...

CVE-2026-107399

The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize applies no origin trust boundary in Mechanize::HTTP::Agentresponsefollowmetarefresh when Mechanizefollowmetarefresh is enabled. A page containing a meta refresh to another origin causes headers...

CVE-2026-107399

The Mechanize library (prior to version 2.14.1 ) fails to enforce an origin trust boundary within the Mechanize::HTTP::Agent#response_follow_meta_refresh function when follow_meta_refresh is enabled. This flaw allows a page containing a meta refresh to an external origin to cause the library to r...

EUVD-2026-95318

The Mechanize library is used for automating interaction with websites. Prior to 2.14.1, Mechanize applies no origin trust boundary in Mechanize::HTTP::Agentresponsefollowmetarefresh when Mechanizefollowmetarefresh is enabled. A page containing a meta refresh to another origin causes headers...