CVE-2025-1868
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVulnerability of unauthorized exposure of confidential information affecting Advanced IP Scanner and Advanced Port Scanner. It occurs when these applications initiate a network scan, inadvertently sending the NTLM hash of the user performing the scan. This vulnerability can be exploited by intercepting network traffic to a legitimate server or by setting up a fake server, in both local and remote scenarios. This exposure is relevant for both HTTP/HTTPS and SMB protocols.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAdvanced IP Scanner and Advanced Port Scanner leak NTLM hashes during network scanning operations by inadvertently transmitting the authenticated user's credentials when connecting to network resources via HTTP/HTTPS or SMB protocols. An attacker with network proximity can intercept these hashes by sniffing traffic to legitimate servers or by positioning a malicious server to capture credentials during scan operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm installation of affected productsCheck program files for Advanced IP Scanner or Advanced Port Scanner directories, or look for installed applications in system settingsAffected if Either Advanced IP Scanner or Advanced Port Scanner is present on the system
-
Identify installed versionLocate the executable (ipscan.exe or aportscan.exe), right-click and view Properties, or check Add/Remove Programs for the version numberAffected if Version matches or falls within any affected version range (compare your version to vendor advisories)
-
Verify NTLM authentication is activeCheck Windows Local Security Policy under Security Options for 'Network security: LAN Manager authentication level' - if set to 'Send LM & NTLM responses' or 'Send LM & NTLM - use NTLMv2 session security if negotiated', NTLM is in useAffected if NTLM authentication is enabled in the environment (not restricted to NTLMv2 only)
-
Confirm scan targets include HTTP/HTTPS or SMB resourcesReview typical scan configurations or logs from Advanced IP Scanner/Port Scanner to see if the tool accesses network shares (SMB) or web servers (HTTP/HTTPS)Affected if Scans routinely target SMB shares or HTTP/HTTPS endpoints on the network
User is affected if either Advanced IP Scanner or Advanced Port Scanner is installed, the environment uses NTLM authentication, and scans access SMB or HTTP/HTTPS resources, allowing potential NTLM hash interception by network attackers
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataEnterprises should restrict use of these tools to isolated network segments, disable NTLM authentication where possible, and monitor for suspicious credential capture attempts. The definitive remediation requires a vendor patch that prevents NTLM hash transmission.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1868 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-1868 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data