CVE-2023-32229
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 · uneditedDue to an error in the software interface to the secure element chip on Bosch IP cameras of family CPP13 and CPP14, the chip can be permanently damaged when enabling the Stream security option (signing of the video stream) with option MD5, SHA-1 or SHA-256.
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 confidenceBosch IP cameras in the CPP13 and CPP14 families have a vulnerability in the software interface to the secure element chip. When users enable the Stream security option to sign video streams using MD5, SHA-1, or SHA-256 algorithms, the secure element chip suffers permanent physical damage due to this interface error.
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< 8.48.0017>= 8.50, < 8.80.0090CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 camera model familyAccess the camera web interface or management console and navigate to System > Product Information or Device Info to confirm the model is part of the CPP13 or CPP14 family.Affected if Camera model is NOT a Bosch CPP13 or CPP14 device (not affected)
-
Check installed firmware versionIn the camera web interface, go to System > Product Information or System > Maintenance > Firmware to view the installed firmware version number.Affected if Firmware version is 8.48.0017 or higher for CPP13, OR firmware version is 8.80.0090 or higher for CPP14 (not affected)
-
Locate Stream security settingsIn the camera web interface, navigate to Configuration > Video > Stream Security or Configuration > Streaming > Stream Security settings panel where video stream signing options are configured.Affected if Stream security feature is not configured or is set to disabled (not affected)
-
Verify signing algorithm configurationIf Stream security is enabled, examine which algorithm is selected for video stream signing. Look for MD5, SHA-1, or SHA-256 options in the algorithm dropdown or configuration field.Affected if Stream security is enabled AND configured to use MD5, SHA-1, or SHA-256 algorithms (AFFECTED)
-
Check for secure element damage symptomsReview camera system logs or diagnostics for errors related to secure element, cryptographic chip, or hardware security module failures. Physical damage may manifest as authentication failures or hardware errors.Affected if Secure element chip shows hardware failure errors after Stream security with affected algorithms was enabled (AFFECTED and damaged)
You are affected if you have a Bosch CPP13 or CPP14 camera with vulnerable firmware AND Stream security is currently enabled using MD5, SHA-1, or SHA-256 algorithms.
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.
dbcve · scoped8.48.00178.80.0090
Do not enable Stream security with MD5, SHA-1, or SHA-256 options on affected Bosch CPP13 and CPP14 cameras until an official firmware patch is released. Permanently damaged secure element chips will require hardware replacement.
Cpp13: firmware >= 8.48.0017 | Cpp14: firmware >= 8.80.0090
- 1. Identify the Bosch IP camera model and confirm it belongs to the CPP13 or CPP14 family
- 2. Check the current firmware version of the camera through the web interface or Bosch configuration tool
- 3. For CPP13 cameras: Download and install firmware version 8.48.0017 or later from psirt.bosch.com
- 4. For CPP14 cameras: Download and install firmware version 8.80.0090 or later from psirt.bosch.com
- 5. After upgrading, verify camera functionality and confirm the Stream security option (signing of video stream) works correctly with the selected hash algorithm
- 6. If immediate upgrade is not possible, do NOT enable the Stream security option with MD5, SHA-1, or SHA-256 algorithms until firmware is updated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32229 — 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-32229 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