CVE-2023-35867
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 · uneditedAn improper handling of a malformed API answer packets to API clients in Bosch BT software products can allow an unauthenticated attacker to cause a Denial of Service (DoS) situation. To exploit this vulnerability an attacker has to replace an existing API server e.g. through Man-in-the-Middle attacks.
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 confidenceThe vulnerability exists in Bosch BT software API clients that improperly handle malformed API response packets. When an attacker performs a Man-in-the-Middle attack to replace the legitimate API server and sends malformed answer packets, the client fails to handle them correctly, causing a denial of service. This is a client-side validation/parsing issue exploitable only in MITM scenarios.
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<= 5.0.1<= 12.0<= 12.0<= 7.62<= 12.0<= 12.0<= 12.0<= 12.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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 the installed Bosch productDetermine which Bosch software product is running in your environment from the list: Building Integration System Video Engine, Video Management System, Video Management System Viewer, Configuration Manager, Divar IP 7000 R2, Divar IP All In One 4000, 5000, or 6000Affected if Any of these products are installed and the version is at or below the affected threshold
-
Check product versionUse the product's built-in version check (typically via About menu, help dialog, or system information) to determine the exact installed version numberAffected if The installed version is at or below 5.0.1 for Building Integration System Video Engine, at or below 12.0 for Video Management System/Viewer/Divar devices, or at or below 7.62 for Configuration Manager
-
Verify network exposureDetermine if the client has network connectivity to external API servers or is deployed in a network segment where a MITM attack could be performedAffected if The client communicates over the network with API servers and is accessible from network segments where an attacker could intercept traffic
-
Confirm API client functionalityCheck if the product uses API client functionality to communicate with backend servers for its core operations (video streaming, configuration sync, device management)Affected if The product relies on API client communications for normal operation
A user is affected if they have any of the listed products installed at or below the specified version AND the product uses API client functionality over a network where a MITM attack is theoretically possible.
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 dataSecure API communication channels with TLS and proper certificate validation to prevent MITM attacks, and implement robust error handling in API clients to gracefully handle malformed responses without crashing.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35867 — 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-35867 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