CVE-2023-28175
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 · uneditedImproper Authorization in SSH server in Bosch VMS 11.0, 11.1.0, and 11.1.1 allows a remote authenticated user to access resources within the trusted internal network via a port forwarding request.
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 confidenceThe SSH server in Bosch Video Management System (VMS) versions 11.0, 11.1.0, and 11.1.1 contains an improper authorization vulnerability where an authenticated remote user can exploit SSH port forwarding to access resources on the trusted internal network. This allows a compromised or malicious authenticated account to bypass network segmentation controls by tunneling through the SSH server to internal systems.
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>= 7.5, <= 11.1.1>= 7.5, <= 11.1.1>= 7.5, <= 8.0= 11.1.1= 11.1.1>= 9.0, <= 11.1.1>= 7.5, <= 11.1.1>= 7.5, <= 8.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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Bosch VMS versionOn the system running Bosch VMS, check the installed version via Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or look for version info in the Bosch VMS program directory (typically C:\Program Files\Bosch\VMS). For Divar IP appliances, access system information via the device web interface or login via SSH and run 'version' or 'show system-info' command.Affected if Installed version falls within 7.5 <= version <= 11.1.1 for Bosch VMS or Bosch VMS Viewer, or matches the firmware ranges listed (7.5-8.0, 9.0-11.1.1, or specifically 11.1.1) for Divar IP models.
-
Verify SSH server is enabledCheck if the Bosch VMS SSH service (typically named 'Bosch VMS SSH Server' or 'SSH Server') is running. On Windows, open Services.msc and look for the SSH service. On Divar appliances, attempt to connect to port 22 (or configured SSH port) of the device.Affected if SSH service is installed and running on the Bosch VMS or Divar device.
-
Inspect SSH daemon configuration for port forwardingLocate the sshd_config file (on Bosch VMS typically in C:\Program Files\Bosch\VMS\ssh\etc\sshd_config or similar path). Open the file and search for the 'AllowTcpForwarding' directive. Also check for any 'PermitOpen' restrictions.Affected if AllowTcpForwarding is set to 'yes' or is not explicitly set to 'no', or the directive is missing (defaults to yes in most SSH implementations).
-
Check network exposure of SSH portScan the device IP address on port 22 (or configured SSH port) from an external network location. Verify if the SSH service is accessible from untrusted networks rather than only from management networks. Use 'netstat -an | findstr :22' on the VMS server to check listening interfaces.Affected if SSH port is bound to 0.0.0.0 or is accessible from outside the trusted management network segment.
You are affected if the Bosch VMS or Divar IP device runs a version between 7.5 and 11.1.1, has SSH enabled, and AllowTcpForwarding is not explicitly disabled in the SSH configuration.
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 vendor-supplied patches or updates to Bosch VMS. If no patch is available, restrict SSH port forwarding at the SSH daemon configuration level (disable AllowTcpForwarding), implement network segmentation to limit SSH server reachability, and enforce strict firewall rules between the VMS SSH service and internal network resources.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28175 — 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-28175 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