CVE-2021-23850
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 specially crafted TCP/IP packet may cause a camera recovery image telnet interface to crash. It may also cause a buffer overflow which could enable remote code execution. The recovery image can only be booted with administrative rights or with physical access to the camera and allows the upload of a new firmware in case of a damaged firmware.
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 confidenceBuffer overflow vulnerability in the telnet interface of camera recovery images, triggered by specially crafted TCP/IP packets. While exploitation requires booting the recovery image (needs admin rights or physical access), the vulnerability can cause denial of service or enable remote code execution.
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= cpp7.3= cpp7.3= cpp7.3= cpp7.3= cpp7.3= cpp7.3= cpp7.3= cpp4= cpp7.3CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 camera modelAccess the camera's web interface or use network discovery to determine the exact model (e.g., Autodome IP 4000i, Dinion IP 3000i, etc.)Affected if The model matches any of the following: Autodome IP 4000i, Autodome IP 5000i, Autodome IP Starlight 5000i, Autodome IP Starlight 7000i, Dinion IP 3000i, Dinion IP Bullet 4000i, Dinion IP Bullet 5000, or Dinion IP Bullet 5000i
-
Check firmware versionIn the camera's web interface, navigate to the firmware or system information section to view the installed firmware versionAffected if The firmware version is listed as cpp7.3 or cpp4 (exact match)
-
Verify telnet service availabilityAttempt to connect to the device on TCP port 23 using a telnet client or network scannerAffected if Telnet service is responding on the device (note: this applies to both normal operation and recovery image)
-
Assess recovery image accessibilityDetermine if the recovery image can be booted by checking physical access to the device or admin/root privileges on the networkAffected if An attacker with physical access can power cycle the camera and access recovery mode, or an admin can trigger recovery boot via network
The device is affected if it is one of the listed Bosch camera models running firmware version cpp7.3 or cpp4, and the telnet interface is accessible or recovery image boot is possible by an attacker with physical or administrative access.
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 dataRestrict physical access to camera hardware and enforce strong authentication for recovery image boot procedures. Apply vendor firmware updates when available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23850 — 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-23850 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