nmap-scripts

nmap-scripts cve-2020-0796 & cve-2019-7238 & cve2019-11580 & cve2017-6327 の脆弱性に対する nmap スクリプト CVE-2020-0796 Microsoft Server Message Block 3.1.1 SMBv3 プロトコルが特定のリクエストを処理する方法に、リモートコード実行の脆弱性が存在します。これは 'Windows SMBv3 Client/Server Remote Code Execution Vulnerability' としても知られています。 CVE-2019-7238 Sonaty...

webauthn_tpm_portable

WebAuthn TPM ポータブル認証情報 ⚠️ 初期の概念実証です。 このプロジェクトは十分にテストまたは監査されていません。実験以外の目的では使用しないでください。 TPM 2.0 を使用して複数のデバイスで動作する、移植可能なハードウェアバックアップ付き WebAuthn/パスキー認証情報。 従来の TPM 認証情報は、それを作成したデバイスに固定されています。このプロジェクトでは、マスターシードから派生した決定論的な親キーを各デバイスの TPM にインポートすることで、それらを移植可能にします。これにより、ある TPM...

CVE-2026-67419

RabbitMQ is a messaging and streaming broker. Prior to 4.3.5, an authenticated user who can bind a queue to a topic exchange and publish to it can use consecutive segments in a binding key to make both topic matchers revisit the same trie-node and routing-key-suffix states without memoization. Th...

CVE-2026-67421

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5, RabbitMQ Management rendered an AMQP authorization-error reason containing an attacker-controlled queue name as HTML when the OAuth management UI was enabled. Exploitation requires an...

CVE-2026-67408

RabbitMQ is a messaging and streaming broker. From 4.1.0 until 4.3.3, 4.2.9, and 4.1.11, Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node Denial of Service. rabbitMQ 4.3.1 with rabbitmqstreammanagement enabled accepts PUT /api/stream/super-streams/vhost/name reques...

CVE-2026-67410

RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.3.3 and 4.2.9, OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint CWE-200. when OAuth2 authentication is enabled for the RabbitMQ Management UI and the configured flow, IDP use a client secret, the oauthclientsecre...

CVE-2026-67227

RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.22 and 4.1.14 and 4.2.7 and 4.3.1, Atom exhaustion: toatom on global-parameter :name. resourceexists/2 and the PUT/DELETE handlers call rabbitdatacoercion:toatom/1 on the :name URL path segment. toatom/1 uses binarytoatom/2 unsafe...

CVE-2026-67409

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 4.3.3, 4.2.9, 4.1.14, 4.0.23, and 3.13.18, JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS CWE-252. the JWKS key fetching mechanism in uaajwt.erl does not validate the HTTP response...

CVE-2026-67242 RabbitMQ: OAuth2 is_integer(Exp) guard skips token-expiry checks for float exp

RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.9 and 4.3.3, OAuth2 isintegerExp guard skips token-expiry checks for float exp. validatetokenexpiry/1 lines 208-214 and expirytimestamp/1 138-144 both guard with 'when isintegerExp' and fall through to ok/never for float values...

CVE-2026-67242

RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.9 and 4.3.3, OAuth2 isintegerExp guard skips token-expiry checks for float exp. validatetokenexpiry/1 lines 208-214 and expirytimestamp/1 138-144 both guard with 'when isintegerExp' and fall through to ok/never for float values...

CVE-2026-67230

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15, 4.0.20, 4.1.11, and 4.2.6, the Web STOMP WebSocket handler enforced neither maxframesize nor logintimeout before authentication, allowing an unauthenticated client to keep a connection alive with a slow stream of small frame...

Mitel MiCollab - Authentication Bypass

A vulnerability in the NuPoint Unified Messaging NPM component of Mitel MiCollab through 9.8 SP1 FP2 9.8.1.201 could allow an unauthenticated attacker to conduct a path traversal attack, due to insufficient input validation. A successful exploit could allow unauthorized access, enabling the...

CVE-2026-97155

Fabasoft Folio Client before 2026, a locally installed component that communicates with the Fabasoft browser extension via web messaging, does not restrict which web origins may invoke its functions by default. The registry value VALIDDOMAINS, which limits permitted origins, was optional and empt...

CVE-2026-97155

Fabasoft Folio Client before 2026, a locally installed component that communicates with the Fabasoft browser extension via web messaging, does not restrict which web origins may invoke its functions by default. The registry value VALIDDOMAINS, which limits permitted origins, was optional and empt...

EUVD-2026-85790

Fabasoft Folio Client before 2026, a locally installed component that communicates with the Fabasoft browser extension via web messaging, does not restrict which web origins may invoke its functions by default. The registry value VALIDDOMAINS, which limits permitted origins, was optional and empt...

CVE-2026-97155

The Fabasoft Folio Client (before 2026), including versions shipped with Fabasoft eGov-Suite , is vulnerable to unauthorized function invocation. The root cause is that the VALIDDOMAINS registry value, intended to restrict web origins, is optional and empty by default, causing the client to trust...

CVE-2026-97155

Fabasoft Folio Client before 2026, a locally installed component that communicates with the Fabasoft browser extension via web messaging, does not restrict which web origins may invoke its functions by default. The registry value VALIDDOMAINS, which limits permitted origins, was optional and empt...

CVE-2026-97155: Origin Validation Error

Fabasoft Folio Client before 2026, a locally installed component that communicates with the Fabasoft browser extension via web messaging, does not restrict which web origins may invoke its functions by default. The registry value VALIDDOMAINS, which limits permitted origins, was optional and empt...

PT-2026-97701

Name of the Vulnerable Software and Affected Versions Fabasoft Folio Client versions prior to 2026 Description A locally installed component that communicates with the browser extension via web messaging does not restrict which web origins may invoke its functions by default. The registry value...

artemis-server: artemis-jms-client: artemis-core-client: undertow-core: wildfly-messaging-activemq-subsystem: artemis messaging handlers in Red Hat EAP permit deserialization by default

EAP's Artemis deserialization configuration permits deserialization by default. ObjectMessage.getObject uses ObjectInputStreamWithClassLoader, which implements allow-list/block-list filtering via its checkSecurity/isTrustedType method. However, by default both allow-list and block-list are empty...