A Windows NT domain user or administrator account is configured with a default, null, blank, or missing password. The account therefore lacks an effective password-based authentication secret.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This repository contains a single Metasploit auxiliary scanner module: 'vnc_login.rb'. The module is designed to perform brute-force authentication attempts against VNC servers supporting RFB protocol versions 3.3, 3.7, 3.8, and 4.001. It targets TCP ports 5900 through 5910, which are standard for VNC services. The module allows the user to specify a password or a file of passwords to test, and reports any successful logins. It does not support username-based authentication, as VNC typically uses only passwords. The module references CVE-1999-0506, which relates to weak password vulnerabilities in VNC. The code is written in Ruby and is intended to be run within the Metasploit Framework. No hardcoded payload is delivered; the module's purpose is to identify valid credentials for VNC servers, which can then be used for further exploitation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.