CVE-2023-39445
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 · uneditedHidden functionality vulnerability in LAN-WH300N/RE all versions provided by LOGITEC CORPORATION allows an unauthenticated attacker to execute arbitrary code by sending a specially crafted file to the product's certain management console.
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 confidenceA hidden functionality vulnerability exists in the LOGITEC LAN-WH300N/RE wireless range extender across all versions. The flaw allows an unauthenticated remote attacker to achieve arbitrary code execution by sending specially crafted files to a specific management console interface within the device firmware.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 modelAccess the device admin interface or check the device label/sticker to confirm the exact model number (e.g., Wrc 1467ghbk A, Wrc 1900ghbk S, etc.)Affected if The model matches one of the following: Wrc 1467ghbk A, Wrc 1467ghbk S, Wrc 1900ghbk A, Wrc 1900ghbk S, Wrc 600ghbk A, Wrc 733febk2 A, or Wrc F1167acf2
-
Check the management console interface exposureDetermine if the device management web interface (typically on ports 80/443 or a custom port) is accessible from untrusted network segments or the internetAffected if The management console interface is reachable from outside the trusted local network without authentication
-
Verify remote management is enabledIn the device web interface, check settings related to 'Remote Management', 'Remote Access', or 'WEB Management' to see if it allows external accessAffected if Remote management or external web access is enabled and the interface is network-accessible
-
Confirm firmware version is in the affected rangeIn the device admin panel, navigate to Status or System Information to view the firmware version (note: all versions of the listed models are affected)Affected if The device is one of the affected Elecom WRC models regardless of firmware version
You are affected if you operate any of the listed Elecom WRC models (Wrc 1467ghbk, Wrc 1900ghbk, Wrc 600ghbk, Wrc 733febk2, or Wrc F1167acf2) with their management interface exposed to untrusted networks.
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 dataIf available, apply vendor firmware updates; otherwise, restrict network access to the device's management interface and disable any remote management capabilities to block unauthenticated attacks.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39445 — 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-2023-39445 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