dbcve.org
Bcc101 FirmwareOperating system · Bosch

CVE-2023-49722

MEDIUM · 6.5 CVSS v3.1 Published 2024-01-09
Fix available
A fix is available. Upgrade to 4.13.33 or later.
See remediation →
70/100
Remediation priority · Elevated
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
Network port 8899 open in WiFi firmware of BCC101/BCC102/BCC50 products, that allows an attacker to connect to the device via same WiFi network.

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 confidence

An open network port (8899) in the WiFi firmware of BCC101, BCC102, and BCC50 products allows any device connected to the same WiFi network to establish connections to the device, potentially exposing sensitive functions or data without authentication.

MitigationImmediately restrict network access to port 8899 through firewall rules or network segmentation, and contact the vendor for a firmware update that either disables this port or implements proper authentication.

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
Bcc101 FirmwareOperating system
Affected:>= 4.13.20, < 4.13.33
Bcc102 FirmwareOperating system
Affected:>= 4.13.20, < 4.13.33
Bcc50 FirmwareOperating system
Affected:>= 4.13.20, < 4.13.33

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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 device model
    Locate the product label or check the device management interface to confirm the model is one of: BCC101, BCC102, or BCC50
    Affected if The device model is not BCC101, BCC102, or BCC50, this CVE does not apply
  2. Determine the installed firmware version
    Access the device management interface or check system information to find the firmware version installed on the device
    Affected if The installed firmware version is >= 4.13.20 and < 4.13.33, placing it within the affected range
  3. Verify if port 8899 is listening
    From a device on the same WiFi network, run a port scan against the device's IP address targeting port 8899 (e.g., nmap -p 8899 <device_ip> or telnet <device_ip> 8899)
    Affected if Port 8899 responds and accepts connections, indicating the vulnerable service is exposed
  4. Confirm network accessibility of port 8899
    Attempt to establish a TCP connection to port 8899 from an unauthorized device on the same WiFi network to confirm the port is reachable without authentication
    Affected if Connections can be established to port 8899 without credentials from other WiFi-connected devices, the vulnerability is present

The device is affected if it is a BCC101, BCC102, or BCC50 with firmware version >= 4.13.20 and < 4.13.33, and port 8899 is accessible on the local WiFi network.

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 4.13.33 or later
Fixed in 4.13.33
Interim mitigation

Immediately restrict network access to port 8899 through firewall rules or network segmentation, and contact the vendor for a firmware update that either disables this port or implements proper authentication.

Recommended fix High confidence

Firmware version 4.13.33 or later for BCC101/BCC102/BCC50

  1. 1. Identify the specific device model (BCC101, BCC102, or BCC50)
  2. 2. Check the current firmware version on the device
  3. 3. Download firmware version 4.13.33 or later from the official Bosch support portal (psirt.bosch.com)
  4. 4. Apply the firmware update following Bosch's standard firmware upgrade procedure for the specific device model
  5. 5. Verify that the firmware was applied successfully and port 8899 is no longer exposed

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

Fix this in Bcc101 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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