CVE-2020-25846
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 · uneditedThe digest generation function of NHIServiSignAdapter has not been verified for source file path, which leads to the SMB request being redirected to a malicious host, resulting in the leakage of user's credential.
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 · moderate confidenceThe NHIServiSignAdapter's digest generation function lacks validation of the source file path, allowing an attacker to manipulate the path and redirect SMB authentication requests to a malicious host, resulting in credential leakage.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.20.0218CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/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.
-
Identify if NHIServiSignAdapter is installedSearch for files or services named 'Nhiservisignadapter', 'NHIServiSignAdapter', or related components in system directories (e.g., C:\Program Files, C:\Program Files (x86), or installation folders). Check installed programs list or running services for this component.Affected if The product Panorama Project Nhiservisignadapter is present on the system.
-
Determine installed version of NHIServiSignAdapterLocate the main executable or DLL for NHIServiSignAdapter (typically named Nhiservisignadapter.exe or similar). Right-click the file, select Properties, and check the File Version or Product Version field. Compare this version to the affected version 1.0.20.0218.Affected if The installed version is exactly 1.0.20.0218.
-
Verify the digest generation function is in useCheck application logs, configuration files, or runtime behavior for evidence that the digest generation function (used for file hashing or authentication) is being invoked. Look for operations that process file paths and generate digests, particularly for SMB-related operations.Affected if The digest generation function is actively processing file paths for authentication or hashing operations.
-
Inspect SMB configuration and trusted host settingsExamine configuration files or registry settings related to NHIServiSignAdapter's SMB connections. Look for settings controlling where SMB requests are directed. Check if the configuration allows arbitrary or non-whitelisted host destinations.Affected if SMB requests can be directed to arbitrary/untrusted hosts due to missing host validation in the configuration.
-
Check for path validation in digest generationIf access to source code or configuration is possible, examine the digest generation function's implementation for path validation logic. Look for code that verifies or sanitizes input file paths before processing.Affected if The digest generation function lacks proper source file path validation.
A system is affected if Panorama Project Nhiservisignadapter version 1.0.20.0218 is installed and the digest generation function is being used without proper source file path validation, allowing SMB redirection to untrusted hosts.
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 dataImplement proper source file path verification in the digest generation function and validate that SMB requests are only directed to trusted hosts.
- 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-2020-25846 — 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-2020-25846 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