CVE-2023-46685
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 · uneditedA hard-coded password vulnerability exists in the telnetd functionality of LevelOne WBR-6013 RER4_A_v3411b_2T2R_LEV_09_170623. A set of specially crafted network packets can lead to arbitrary command execution.
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 confidenceA hard-coded password vulnerability exists in the telnetd service of the LevelOne WBR-6013 router firmware (RER4_A_v3411b_2T2R_LEV_09_170623). Attackers can send specially crafted network packets to achieve arbitrary command execution due to this backdoor credentials issue.
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= rer4_a_v3411b_2t2r_lev_09_170623CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 router modelCheck the device label or administrative interface for the model number - verify it is a LevelOne WBR-6013 routerAffected if The device is a LevelOne WBR-6013 unit
-
Check the firmware versionAccess the router's web administrative interface or check via firmware extraction/terminal access, and look for the firmware version string rer4_a_v3411b_2t2r_lev_09_170623Affected if The installed firmware matches exactly rer4_a_v3411b_2t2r_lev_09_170623
-
Verify telnetd service statusCheck the router's administrative interface for telnet/remote management settings, or attempt to connect to TCP port 23 on the device to see if telnetd is listeningAffected if Telnetd service is enabled and accessible on the device
-
Test for hardcoded credentialsAttempt to connect to the telnet service using the known backdoor credentials associated with this CVE (if you have them from the vulnerability report) - do not guess or use common default credentialsAffected if Authentication succeeds with the hardcoded backdoor password for this specific firmware version
You are affected if you are running the LevelOne WBR-6013 router with firmware rer4_a_v3411b_2t2r_lev_09_170623 and the telnetd service is enabled and accessible on your network.
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 dataDisable the telnetd service via the router's administrative interface if available; otherwise, restrict network access to the telnet port or replace the device with a model receiving vendor security updates.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46685 — 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-46685 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