CVE-2024-33374
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 · uneditedIncorrect access control in the UART/Serial interface on the LB-LINK BL-W1210M v2.0 router allows attackers to access the root terminal without authentication.
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 LB-LINK BL-W1210M v2.0 router contains an authentication bypass vulnerability in its UART/Serial interface. The serial debug interface lacks access control, allowing anyone with physical access to the UART pins or network-accessible serial service to obtain a root shell without credentials.
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
- 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 device model and firmware versionCheck the device label or login to the router admin interface to confirm the exact model number (BL-W1210M) and firmware version. Compare against the affected product (v2.0).Affected if The device is an LB-LINK BL-W1210M v2.0 router or variant.
-
Locate UART/Serial debug pinsPhysically inspect the router PCB for exposed UART pins (typically 4 pins: TX, RX, GND, VCC). Check device documentation or PCB silkscreen for serial debug headers.Affected if UART pins are physically accessible on the device PCB.
-
Test serial console for authentication bypassConnect to UART pins using a USB-to-serial adapter at common baud rates (9600, 115200). Power on the device and observe the boot logs. Attempt to access a root shell or command prompt without providing credentials.Affected if The serial console provides a root shell or privileged command prompt without requiring any username or password.
-
Check for network-accessible serial serviceScan the router for open ports that may expose serial services (non-standard ports, port 23 telnet-like services). Use nmap or netstat to enumerate listening services on the device.Affected if A network service is listening that provides serial/UART access without authentication.
-
Verify serial console behavior at bootObserve the serial output during device boot sequence. Check if the boot process automatically spawns a root shell or drops to an unauthenticated shell prompt.Affected if The boot sequence automatically launches an interactive shell with root privileges without any authentication.
A user is affected if they have physical access to a BL-W1210M v2.0 device with exposed UART pins or have a network-accessible serial service that provides root shell access without credentials.
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 authentication requirements for the UART/Serial interface, disable the serial console at boot, or restrict physical access to the device. Network-accessible serial services should be disabled if not required.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33374 — 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-2024-33374 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