dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2024-32010

HIGH · 7.8 CVSS v3.1 Published 2025-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 Spectrum Power 4 (All versions < V4.70 SP12 Update 2). The affected application is vulnerable to extraction of database credentials via a world-readable credential file. This allows an attacker to connect to the database as privileged application user and to run system commands via 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 · high confidence

Spectrum Power 4 stores database credentials in a file with world-readable permissions, allowing any local user to extract the credentials. An attacker can then connect to the database as the privileged application user and execute system commands through database functionality.

MitigationRestrict file permissions on credential storage files to root/admin only, or upgrade to V4.70 SP12 Update 2 or later which addresses the hardcoded credential exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:L/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. Identify Spectrum Power 4 installation
    Locate the Spectrum Power 4 installation directory, typically under C:\Program Files\Siemens\Spectrum Power or /opt/spectrum_power on Linux. Check for the presence of SPWR4 executable or service.
    Affected if Spectrum Power 4 is installed and running on the system
  2. Find database credential storage file
    Search for configuration files in the Spectrum Power 4 installation directory that contain database connection strings or credentials. Common locations: config/ directory, *.properties, *.xml, or *.ini files with 'database', 'db', 'password', or 'credential' in the filename.
    Affected if A database configuration file exists in the Spectrum Power 4 installation
  3. Check file permissions on credential file
    On Linux/Unix: use 'ls -la <credential_file>' to view permissions. On Windows: right-click the file > Properties > Security, or use 'icacls <file>' command. Verify if 'Everyone', 'Users', or 'Authenticated Users' have Read access.
    Affected if The credential file grants Read permission to non-admin users (world-readable or group-readable)
  4. Verify installed version
    Check the Spectrum Power 4 version through the application UI (Help > About), or locate a version file in the installation directory. Look for version information in any .version, version.txt, or similar file.
    Affected if The installed version is earlier than V4.70 SP12 Update 2, or the version cannot be determined

A user is affected if Spectrum Power 4 is installed with a version prior to V4.70 SP12 Update 2 AND the database credential file has read permissions granted to non-administrative users.

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

Restrict file permissions on credential storage files to root/admin only, or upgrade to V4.70 SP12 Update 2 or later which addresses the hardcoded credential exposure.

Recommended fix High confidence

V4.70 SP12 Update 2 or later

  1. Identify the current version of Spectrum Power 4 installed in the environment
  2. Plan maintenance window for upgrade procedure
  3. Perform full backup of the Spectrum Power 4 system including database and configuration
  4. Upgrade Spectrum Power 4 to version V4.70 SP12 Update 2 or later
  5. After upgrade, verify that credential files are no longer world-readable (permissions should be restricted)
  6. Confirm the application functions correctly post-upgrade
  7. Verify database credentials are now stored with proper restricted permissions
Caveat Standard upgrade risks apply - test in non-production environment first

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

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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