dbcve.org
360 Indoor Camera FirmwareOperating system · Bosch

CVE-2018-20299

CRITICAL · 9.8 CVSS v3.1 Published 2018-12-19
Fix available
A fix is available. Upgrade to 6.52.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
An issue was discovered in several Bosch Smart Home cameras (360 degree indoor camera and Eyes outdoor camera) with firmware before 6.52.4. A malicious client could potentially succeed in the unauthorized execution of code on the device via the network interface, because there is a buffer overflow in the RCP+ parser of the web server.

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

A buffer overflow vulnerability exists in the RCP+ parser of the web server in Bosch Smart Home cameras (360 degree indoor and Eyes outdoor). The flaw allows a remote, unauthenticated attacker to potentially execute arbitrary code on the device via the network interface due to insufficient bounds checking in the protocol parser.

MitigationUpgrade affected camera firmware to version 6.52.4 or later. If upgrading is not immediately possible, restrict network access to the cameras and monitor for indicators of compromise.

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
360 Indoor Camera FirmwareOperating system
Affected:< 6.52.4
Eyes Outdoor Camera FirmwareOperating system
Affected:< 6.52.4

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
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 checks

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

  1. Identify your camera model
    Locate the Bosch camera in use - either the 360 Indoor Camera or Eyes Outdoor Camera. Check the device label, packaging, or the Bosch Smart Home app device details for the exact model name.
    Affected if The device is not a Bosch 360 Indoor Camera or Eyes Outdoor Camera, then this CVE does not apply.
  2. Access the camera firmware version
    Open the Bosch Smart Home app, select the camera device, and navigate to Settings > Device Information > Software version. Alternatively, access the camera's web interface and look for a firmware or version information page.
    Affected if Unable to retrieve the firmware version from the app or web interface.
  3. Compare firmware version to affected range
    Note the installed firmware version (for example, 6.51.2 or 6.52.3) and compare it to the vulnerable threshold of 6.52.4. Any version below 6.52.4 (including 6.50.x, 6.51.x, and 6.52.x versions prior to 6.52.4) is affected.
    Affected if The installed firmware version is less than 6.52.4, meaning the camera is running a vulnerable version.
  4. Confirm network accessibility of the web server
    Verify that the camera's web server is accessible on the network. This is typically enabled by default and listens on the local network IP address of the camera. Attempt to access http://[camera-ip] in a browser.
    Affected if The web server is accessible on the network, which enables the RCP+ parser attack surface. If the web server is disabled or isolated, the exploitability may be reduced but the vulnerable code still exists in the firmware.

You are affected if you have a Bosch 360 Indoor Camera or Eyes Outdoor Camera running firmware version below 6.52.4 and the camera's web server is network-accessible.

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.

dbcve · scoped
Upgrade available Upgrade to 6.52.4 or later
Fixed in 6.52.4
Interim mitigation

Upgrade affected camera firmware to version 6.52.4 or later. If upgrading is not immediately possible, restrict network access to the cameras and monitor for indicators of compromise.

Recommended fix High confidence

Firmware version 6.52.4 or later for 360 Indoor Camera and Eyes Outdoor Camera

  1. Identify the specific Bosch camera model (360 Indoor Camera or Eyes Outdoor Camera) that needs remediation
  2. Access the camera's web interface or Bosch Smart Home app to check the current firmware version
  3. Navigate to the official Bosch support or download page for your camera model
  4. Download the firmware version 6.52.4 or later from Bosch's official source
  5. Follow Bosch's official firmware update instructions to apply the update to the camera
  6. After updating, verify that the firmware has been successfully upgraded to version 6.52.4 or newer

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in 360 Indoor Camera Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-20299 — 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-2018-20299 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