CVE-2021-25848
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 · uneditedImproper validation of the length field of LLDP-MED TLV in userdisk/vport_lldpd in Moxa Camera VPort 06EC-2V Series, version 1.1, allows information disclosure to attackers due to using fixed loop counter variable without checking the actual available length via a crafted lldp packet.
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 vulnerability exists in the LLDP-MED TLV parsing logic within the userdisk/vport_lldpd component of the Moxa Camera VPort 06EC-2V Series. The application uses a fixed loop counter to process TLV data without validating the declared length field against the actual available buffer length, allowing an attacker to read out-of-bounds memory contents via a specially crafted LLDP packet.
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.1<= 1.1<= 1.1<= 1.1<= 1.1<= 1.1<= 1.1<= 1.1CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 camera modelCheck the device label or web interface to confirm the exact model number is one of the Vport 06ec variants (2v26m, 2v36m, 2v36m Ct, 2v36m Ct T, 2v42m, 2v42m T, 2v42m Ct, or 2v42m Ct T)Affected if The model is not one of the listed Vport 06ec variants, then it is not affected by this specific CVE
-
Check the firmware versionAccess the camera's web interface (typically under System > Firmware or Settings > About) or use the manufacturer's management tool to retrieve the installed firmware versionAffected if The firmware version is 1.1 or lower, the device falls within the affected version range
-
Verify if LLDP service is enabledCheck the camera's network settings or examine running processes to determine if the LLDP (vport_lldpd) service is active on the deviceAffected if LLDP is disabled, the vulnerable parsing code is not exposed and exploitation is not possible
-
Assess network exposure to LLDP trafficReview network segmentation and firewall rules to determine if untrusted network segments can send LLDP packets to the camera (LLDP uses multicast to 01:80:c2:00:00:0e)Affected if The camera is directly accessible from untrusted networks without LLDP traffic filtering, an attacker could send malicious LLDP packets
The environment is affected only if the device is a Vport 06ec model running firmware version 1.1 or lower, the LLDP service is enabled, and the device is reachable from network segments where untrusted LLDP packets could be injected.
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 dataApply vendor firmware patches when available; otherwise, restrict network access to the camera and block unauthorized LLDP traffic at network boundaries to prevent exploitation.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-25848 — 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-2021-25848 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