dbcve.org
Sicam Pas\/pqsApplication · Siemens

CVE-2016-8567

CRITICAL · 9.8 CVSS v3.1 Published 2017-02-13
Fix available
A fix is available. Upgrade to 8.00 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An issue was discovered in Siemens SICAM PAS before 8.00. A factory account with hard-coded passwords is present in the SICAM PAS installations. Attackers might gain privileged access to the database over Port 2638/TCP.

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

Siemens SICAM PAS versions before 8.00 contain a hard-coded factory account with static passwords embedded in the software. Attackers can use these credentials to authenticate to the database over port 2638/TCP, gaining privileged access to the entire system.

MitigationUpdate to SICAM PAS 8.00 or later to remove the hard-coded credentials, change all default passwords immediately, and restrict network access to port 2638/TCP using firewalls or network segmentation.

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 Pas\/pqsApplication
Affected:< 8.00

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify SICAM PAS installation and version
    Locate the SICAM PAS installation directory and check the version information file, typically found in the program's main folder or via Windows Programs and Features. Look for version details in README, version.info, or the main executable properties.
    Affected if Installed version is before 8.00 (any version < 8.00)
  2. Verify database port 2638/TCP is listening
    Run 'netstat -an | findstr 2638' or use a port scanner to check if port 2638/TCP is open and listening on the SICAM PAS server. This port hosts the Sybase database.
    Affected if Port 2638/TCP is open and accessible on the network
  3. Check for hard-coded database accounts
    Inspect the SICAM PAS configuration files, particularly database connection configuration files in the installation directory, for embedded credentials. Look for factory default account names and static passwords in XML, INI, or configuration databases.
    Affected if Hard-coded credentials or default factory accounts are found in configuration files
  4. Review database user authentication
    Query the Sybase database (via isql or management tools on port 2638) to enumerate database users. Look for factory accounts with known default passwords that should not exist in a production environment.
    Affected if Pre-existing database accounts with default/static passwords exist beyond initial setup

A system is affected if SICAM PAS version is below 8.00 AND the database port 2638/TCP is exposed on the network, allowing attackers to use hard-coded credentials for privileged access.

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
Upgrade available Upgrade to 8.00 or later
Fixed in 8.00
Interim mitigation

Update to SICAM PAS 8.00 or later to remove the hard-coded credentials, change all default passwords immediately, and restrict network access to port 2638/TCP using firewalls or network segmentation.

Recommended fix Moderate confidence

8.00

  1. 1. Back up the current SICAM PAS installation and database before starting the upgrade process.
  2. 2. Obtain the Siemens SICAM PAS version 8.00 or later upgrade package from the official Siemens support channels.
  3. 3. Review the Siemens upgrade documentation specific to your deployment to understand prerequisites and migration procedures.
  4. 4. Execute the upgrade following Siemens installation guidelines, ensuring all pre-upgrade checks pass.
  5. 5. After completing the upgrade, immediately change the factory account password identified in the CVE or disable the account if not needed.
  6. 6. Verify that database access over Port 2638/TCP is properly secured and restricted to authorized systems only.
  7. 7. Validate that the upgrade was successful and the system is functioning normally.
Caveat Review Siemens release notes for version 8.00 to check for any compatibility changes with existing configurations, plugins, or integrations before upgrading.

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

Fix this in Sicam Pas\/pqs Scoped from the published advisory
  • Consultation10.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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