CVE-2021-32941
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 · uneditedAnnke N48PBB (Network Video Recorder) products of version 3.4.106 build 200422 and prior are vulnerable to a stack-based buffer overflow, which allows an unauthorized remote attacker to execute arbitrary code with the same privileges as the server user (root).
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 confidenceStack-based buffer overflow vulnerability in Annke N48PBB NVR firmware versions 3.4.106 build 200422 and prior allows unauthenticated remote attackers to achieve arbitrary code execution with root privileges, representing a critical pre-authentication remote code execution flaw.
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< 3.4.106= 3.4.106CVSS 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.
-
Check NVR firmware version via web interfaceLog into the Annke N48PBB NVR web interface (typically http://<device-ip>), navigate to System or Settings, then look for a Firmware Version, System Info, or About section. Note the exact firmware version number displayed.Affected if The displayed firmware version is 3.4.106 or lower, or shows build 200422 or earlier.
-
Verify the specific firmware build numberIn the same System Info or About section, locate the Build Date or Build Number field. Confirm whether it reads 200422 or any date/build prior to that.Affected if The build number is 200422 or earlier, indicating an unpatched version.
-
Cross-check via NVR local display if availableIf the NVR has a local monitor output, access the device locally, go to Menu > System > Info (or similar path depending on OSD), and record the firmware version and build number shown.Affected if The locally displayed version matches 3.4.106 or lower with build 200422 or earlier.
-
Confirm device model matches N48PBBVerify the affected device model is specifically the Annke N48PBB (or N48PBB variant). Check the product label on the physical device or the model number displayed in the system information.Affected if The device is an Annke N48PBB model running firmware version 3.4.106 or prior.
A user is affected if their Annke N48PBB NVR runs firmware version 3.4.106 or any version build 200422 or earlier.
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 data3.4.106
Update the device firmware to a version beyond 3.4.106 build 200422 once the vendor releases a patch; until then, isolate the NVR from untrusted networks using network segmentation and firewall rules to reduce attack surface.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-32941 — 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-32941 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