CVE-2021-23853
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 · uneditedIn Bosch IP cameras, improper validation of the HTTP header allows an attacker to inject arbitrary HTTP headers through crafted URLs.
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 confidenceThis is an HTTP header injection (CRLF injection) vulnerability in Bosch IP cameras. The improper validation of input in HTTP requests allows attackers to inject carriage return and line feed characters (%0D%0A) through crafted URLs, enabling injection of arbitrary HTTP headers. This can lead to HTTP response splitting attacks, cache poisoning, and potentially cross-site scripting.
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 dataall versionsall versionsall versionsall versionsall versionsCVSS 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 Bosch IP camera modelCheck device inventory, network scan results, or access the device web interface and look for Bosch branding in the header or device information pageAffected if Device is a Bosch IP camera
-
Determine firmware versionAccess the device web interface, navigate to System or Maintenance section, then to Firmware/Version information. Alternatively, check the SNMP or ONVIF device information if availableAffected if Firmware version string contains Cpp4, Cpp6, Cpp7, Cpp7.3, or Cpp13
-
Confirm firmware variant typeLook at the exact firmware designation shown in the version information - it will typically display as 'Cpp4', 'Cpp6', 'Cpp7', 'Cpp7.3', or 'Cpp13'Affected if The firmware variant is any of these five (Cpp4, Cpp6, Cpp7, Cpp7.3, Cpp13)
-
Check for CRLF injection attempts in logsReview device HTTP access logs or central log aggregation for requests containing '%0D%0A' or raw CRLF characters in URLs or parametersAffected if Suspicious injection patterns are found in the logs indicating exploitation attempts
You are affected if your Bosch IP camera runs Cpp4, Cpp6, Cpp7, Cpp7.3, or Cpp13 firmware - all versions of these firmware variants are vulnerable to HTTP header injection.
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 the vendor firmware update from Bosch for affected IP camera models. If a patch is unavailable, consider network segmentation to limit exposure and implement WAF rules to filter CRLF injection attempts in HTTP requests.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23853 — 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-23853 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