CVE-2023-39509
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 · uneditedA command injection vulnerability exists in Bosch IP cameras that allows an authenticated user with administrative rights to run arbitrary commands on the OS of 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 · moderate confidenceA command injection vulnerability in Bosch IP cameras permits authenticated administrators to execute arbitrary operating system commands, potentially allowing full compromise of the device.
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<= 8.90>= 8.20, <= 8.81CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device as a Bosch IP cameraAccess the camera's web interface or check the device's network information. Bosch IP cameras typically expose a web admin panel on port 80/443 or can be queried via ONVIF/SNMP. Look for Bosch branding or manufacturer strings in the device discovery.Affected if The device is not a Bosch IP camera - this CVE does not apply.
-
Determine the firmware family (Cpp13 or Cpp14)In the camera's web admin panel, navigate to the firmware or system information page. The firmware name or build identifier will indicate whether it is Cpp13 or Cpp14. This may also be visible via the camera's FTP, RTSP, or API endpoints.Affected if The firmware family cannot be determined or is not Cpp13/Cpp14.
-
Check the installed firmware versionLocate the exact firmware version number in the camera's admin interface under System > Firmware, System > Information, or similar. Note the full version string (e.g., 8.90, 8.81, 8.20).Affected if The firmware version cannot be retrieved from the device.
-
Compare version against affected rangesFor Cpp13: check if version <= 8.90. For Cpp14: check if version is >= 8.20 AND <= 8.81. If the camera is on a newer patched version outside these ranges, it is not affected.Affected if The installed version falls within Cpp13 <= 8.90 OR Cpp14 >= 8.20 through <= 8.81.
-
Verify administrative access is enabledThis vulnerability requires authenticated administrator access to the camera. Check if there are any administrator accounts configured, and review access logs or session records for administrative logins via the web interface, API, or protocols like ONVIF.Affected if Administrative accounts exist and the camera is accessible to authenticated administrators.
A user is affected if they have a Bosch IP camera running Cpp13 firmware <= 8.90 or Cpp14 firmware between 8.20 and 8.81, with administrative access enabled.
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 dataRestrict administrative access to trusted personnel only, apply vendor firmware patches when available, and monitor for unauthorized administrative sessions.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
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 locallyCheck whether your project pulls in CVE-2023-39509 — 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-39509 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