dbcve.org
Siveillance VideoApplication · Siemens

CVE-2023-30899

HIGH · 8.8 CVSS v3.1 Published 2023-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A vulnerability has been identified in Siveillance Video 2020 R2 (All versions < V20.2 HotfixRev14), Siveillance Video 2020 R3 (All versions < V20.3 HotfixRev12), Siveillance Video 2021 R1 (All versions < V21.1 HotfixRev12), Siveillance Video 2021 R2 (All versions < V21.2 HotfixRev8), Siveillance Video 2022 R1 (All versions < V22.1 HotfixRev7), Siveillance Video 2022 R2 (All versions < V22.2 HotfixRev5), Siveillance Video 2022 R3 (All versions < V22.3 HotfixRev2), Siveillance Video 2023 R1 (All versions < V23.1 HotfixRev1). The Management Server component of affected applications deserializes data without sufficient validations. This could allow an authenticated remote attacker to execute code on the affected system.

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

The Management Server component of Siveillance Video deserializes data without sufficient validation, allowing an authenticated remote attacker to execute arbitrary code on the affected system through insecure deserialization.

MitigationApply the vendor-supplied hotfix for the specific Siveillance Video version in use: V20.2 HotfixRev14, V20.3 HotfixRev12, V21.1 HotfixRev12, V21.2 HotfixRev8, V22.1 HotfixRev7, V22.2 HotfixRev5, V22.3 HotfixRev2, or V23.1 HotfixRev1.

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
Siveillance VideoApplication
Affected:= 2020= 2021= 2022= 2023

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Siveillance Video Management Server is installed
    Check installed programs or services for Siemens Siveillance Video Management Server component
    Affected if The Management Server component of Siveillance Video is present on the system
  2. Identify installed Siveillance Video version
    Use system inventory, installed programs list, or check version metadata of the Management Server service
    Affected if The version matches 2020, 2021, 2022, or 2023 (or specific releases like V20.x, V21.x, V22.x, V23.x)
  3. Confirm Management Server network exposure
    Check if the Management Server service is listening on network ports and accessible from network locations
    Affected if Management Server is network-accessible without being limited to localhost or restricted administrative networks
  4. Verify authentication is enabled
    Review Management Server security configuration to confirm authentication is properly configured
    Affected if The system relies on the authentication mechanism that can be bypassed or compromised by an authenticated attacker
  5. Check if hotfix has been applied
    Review installed updates or hotfixes for the specific version against vendor hotfix list (V20.2 Rev14, V20.3 Rev12, V21.1 Rev12, V21.2 Rev8, V22.1 Rev7, V22.2 Rev5, V22.3 Rev2, V23.1 Rev1)
    Affected if The installed hotfix version is lower than or missing from the vendor-recommended list for the respective release

The environment is affected if Siveillance Video Management Server version 2020-2023 is installed, network-accessible, and lacks the vendor-supplied hotfix for that specific version.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied hotfix for the specific Siveillance Video version in use: V20.2 HotfixRev14, V20.3 HotfixRev12, V21.1 HotfixRev12, V21.2 HotfixRev8, V22.1 HotfixRev7, V22.2 HotfixRev5, V22.3 HotfixRev2, or V23.1 HotfixRev1.

Recommended fix High confidence

Apply the version-specific hotfix: V20.2 HotfixRev14 / V20.3 HotfixRev12 / V21.1 HotfixRev12 / V21.2 HotfixRev8 / V22.1 HotfixRev7 / V22.2 HotfixRev5 / V22.3 HotfixRev2 / V23.1 HotfixRev1 (depending on your release line)

  1. Identify the exact installed version of Siveillance Video (2020 R2/R3, 2021 R1/R2, 2022 R1/R2/R3, or 2023 R1) using the Management Server component
  2. Navigate to the Siemens Security Advisory on cert-portal.siemens.com or contact Siemens support to obtain the required hotfix
  3. For Siveillance Video 2020 R2: Apply hotfix V20.2 HotfixRev14 or later
  4. For Siveillance Video 2020 R3: Apply hotfix V20.3 HotfixRev12 or later
  5. For Siveillance Video 2021 R1: Apply hotfix V21.1 HotfixRev12 or later
  6. For Siveillance Video 2021 R2: Apply hotfix V21.2 HotfixRev8 or later
  7. For Siveillance Video 2022 R1: Apply hotfix V22.1 HotfixRev7 or later
  8. For Siveillance Video 2022 R2: Apply hotfix V22.2 HotfixRev5 or later

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

Fix this in Siveillance Video Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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