Sicam Toolbox IiApplication · Siemens

CVE-2021-45106

MEDIUM · 6.5 CVSS v3.1 Published 2022-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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 SICAM TOOLBOX II (All versions). Affected applications use a circumventable access control within a database service. This could allow an attacker to access the database.

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

SICAM TOOLBOX II contains a database service with a circumventable access control mechanism. An attacker could potentially bypass the access controls and gain unauthorized access to the database, potentially allowing data exposure or manipulation.

MitigationImplement proper authentication and authorization checks within the database service layer. Restrict database access to authorized users and applications only, and validate all access requests server-side.

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
Sicam Toolbox IiApplication
Affected:all versions

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if SICAM TOOLBOX II is installed
    Check the installed programs or application list on the system for Siemens SICAM TOOLBOX II. On Windows, use the Add/Remove Programs list or check the installation directory where Siemens software is typically installed.
    Affected if SICAM TOOLBOX II is present on the system
  2. Locate the database service component
    Identify the database service that ships with SICAM TOOLBOX II. Look for database executables, services, or processes related to the application in the installation directory or running services.
    Affected if A database service component bundled with SICAM TOOLBOX II is found running on the system
  3. Verify database service accessibility
    Test if the database service can be accessed without authentication. Attempt to connect to the database port or interface used by SICAM TOOLBOX II without providing credentials.
    Affected if The database service accepts connections without requiring proper authentication credentials
  4. Check network exposure of the database service
    Review network listeners and firewall rules to determine if the database service port is bound to network interfaces accessible from non-localhost sources.
    Affected if The database service is listening on a network interface other than localhost and is accessible remotely
  5. Inspect access control configuration
    Examine the database service configuration files or settings for any authentication enforcement mechanisms, role-based access controls, or password protection settings.
    Affected if Access control mechanisms are absent, disabled, or improperly configured in the database service

If SICAM TOOLBOX II is installed and its database service can be accessed without proper authentication or authorization, the environment is affected by this vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication and authorization checks within the database service layer. Restrict database access to authorized users and applications only, and validate all access requests server-side.

Fix this in Sicam Toolbox Ii Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-45106 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-45106 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