dbcve.org
Cpp4 FirmwareOperating system · Bosch

CVE-2021-23849

HIGH · 8.8 CVSS v3.1 Published 2021-08-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
A vulnerability in the web-based interface allows an unauthenticated remote attacker to trigger actions on an affected system on behalf of another user (CSRF - Cross Site Request Forgery). This requires the victim to be tricked into clicking a malicious link or opening a malicious website while being logged in into the camera.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the web-based interface of affected camera systems. An unauthenticated remote attacker can trick a logged-in user into unknowingly triggering unauthorized actions by sending malicious requests through the victim's authenticated session.

MitigationImplement anti-CSRF tokens on all state-changing operations, configure SameSite cookie attributes, and add referrer/origin validation checks to prevent forged requests from malicious sites.

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
Cpp4 FirmwareOperating system
Affected:= 7.10
Cpp6 FirmwareOperating system
Affected:= 7.60= 7.61= 7.70= 7.80
Aviotec FirmwareOperating system
Affected:= 7.61= 7.72
Cpp7 FirmwareOperating system
Affected:= 7.60= 7.61= 7.70= 7.72= 7.80
Cpp7.3 FirmwareOperating system
Affected:= 7.60= 7.61= 7.62= 7.70= 7.72= 7.73= 7.80
Cpp13 FirmwareOperating system
Affected:= 7.75
Cpp14 FirmwareOperating system
Affected:= 8.00

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the camera firmware version
    Access the camera web interface and navigate to System Overview or About section, or use the camera's API/SDK documentation to query the firmware version programmatically
    Affected if The firmware version matches any of these: Cpp4=7.10, Cpp6=7.60/7.61/7.70/7.80, Aviotec=7.61/7.72, Cpp7=7.60/7.61/7.70/7.72/7.80, Cpp7.3=7.60/7.61/7.62/7.70/7.72/7.73/7.80, Cpp13=7.75, Cpp14=8.00
  2. Check if web interface uses anti-CSRF tokens
    Log into the camera web interface, inspect HTML forms and AJAX requests using browser developer tools, and look for hidden token fields or request headers that change with each session
    Affected if No anti-CSRF tokens are present in state-changing forms (such as settings changes, user management, or configuration updates) and requests lack unique token parameters
  3. Verify SameSite cookie attribute configuration
    Using browser developer tools, examine the Set-Cookie headers and cookie attributes for the camera web session; check if SameSite attribute is set to Strict or Lax
    Affected if SameSite attribute is missing or set to None on authentication cookies, allowing cross-site cookie transmission
  4. Test for referrer/origin validation on state-changing actions
    Attempt to trigger a configuration change via the web interface while observing whether the server validates the Origin or Referer header by manually removing these headers in a request tool
    Affected if The server accepts state-changing requests without validating the Origin or Referer header, or returns success when these headers are missing or point to an external domain

You are affected if your camera firmware version matches any of the listed versions AND the web interface lacks anti-CSRF token protection, SameSite cookie attributes, and referrer/origin validation on state-changing operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens on all state-changing operations, configure SameSite cookie attributes, and add referrer/origin validation checks to prevent forged requests from malicious sites.

Fix this in Cpp4 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing4.0 h
  • Review / QA2.0 h
22.0 hours of engineering $3,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-23849 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-23849 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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