CVE-2022-38625
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 · uneditedPatlite NH-FB v1.46 and below was discovered to contain insufficient firmware validation during the upgrade firmware file upload process. This vulnerability allows authenticated attackers to create and upload their own custom-built firmware and inject malicious code. NOTE: the vendor's position is that this is a design choice, not a vulnerability
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 Patlite NH-FB v1.46 and below lacks proper firmware validation during the firmware upgrade upload process. This allows any authenticated attacker to craft and upload malicious custom firmware containing arbitrary code, which will then be executed by the device.
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.46<= 1.46<= 1.46CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 the device modelLocate the physical device or check network inventory for Patlite NH-FB, Nbm D88n, Nhl 3fb1, or Nhl 3fv1n models. This can be done via SNMP, physical inspection of the device label, or logging into the device web interface to view the model information.Affected if The device is a Patlite NH-FB or one of the listed variants (Nbm D88n, Nhl 3fb1, Nhl 3fv1n).
-
Check the installed firmware versionAccess the device management interface (typically via web browser) and navigate to the firmware or system information page to view the current firmware version. Alternatively, check via SNMP or the device API if available.Affected if The firmware version is 1.46 or lower.
-
Verify if remote management interface is accessibleDetermine if the device web interface or management port is reachable from the network. Check firewall rules, VLAN segmentation, and whether the management IP is exposed to untrusted networks.Affected if The device management interface is accessible from network segments accessible to potential attackers, as an authenticated attacker is required to exploit this vulnerability.
-
Confirm firmware upgrade functionality is enabledCheck if the firmware upload or upgrade feature is available and enabled on the device. This is typically found in the maintenance or admin section of the web interface.Affected if The firmware upgrade/upload feature is present and enabled on the device.
You are affected if you have a Patlite NH-FB, Nbm D88n, Nhl 3fb1, or Nhl 3fv1n device running firmware version 1.46 or lower, and the device management interface with firmware upgrade capability is accessible to authenticated users.
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 cryptographic signing and verification of firmware images before acceptance - the device should verify a cryptographic signature or hash of the uploaded firmware against a trusted key stored on the device prior to flashing. Network access controls and authentication hardening can reduce attack surface.
- Consultation6.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,016.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38625 — 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-2022-38625 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