CVE-2019-6579
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 vulnerability has been identified in Spectrum Power 4 (with Web Office Portal). An attacker with network access to the web server on port 80/TCP or 443/TCP could execute system commands with administrative privileges. The security vulnerability could be exploited by an unauthenticated attacker with network access to the affected service. No user interaction is required to exploit this security vulnerability. Successful exploitation of the security vulnerability compromises confidentiality, integrity or availability of the targeted system. At the time of advisory publication no public exploitation of this security vulnerability was known.
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 confidenceSpectrum Power 4 with Web Office Portal contains a critical remote code execution vulnerability where an unauthenticated attacker with network access to ports 80/TCP or 443/TCP can execute system commands with administrative privileges. The vulnerability requires no user interaction and affects the web server component of this industrial control system software.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Siemens Spectrum Power 4 is installedCheck system inventory or installed programs for 'Spectrum Power 4' or look for the product directory structure on the host. Common installation paths may include C:\Siemens\Spectrum Power 4 or /opt/spectrum-power4/ on Windows or Linux systems respectively.Affected if Spectrum Power 4 is installed on the system
-
Confirm the Web Office Portal component is presentLook for web server components such as IIS or Apache configurations associated with Spectrum Power, or check for the presence of web portal directories and configuration files in the Spectrum Power installation folder.Affected if The Web Office Portal component exists in the installation
-
Verify the web service is running and accessibleCheck if the web server is listening on ports 80/TCP or 443/TCP on the affected host. Use netstat or similar tools: 'netstat -an | findstr "80\|443"' on Windows or 'netstat -tlnp | grep -E "80|443"' on Linux.Affected if Ports 80 or 443 are open and listening for the Spectrum Power web service
-
Determine network accessibility of the web portalFrom an external or different network segment, attempt to reach the web portal via HTTP (port 80) or HTTPS (port 443) using a browser or curl command: curl http://<target-ip> or curl https://<target-ip>.Affected if The web portal is reachable from an unauthorized network location
If Spectrum Power 4 with Web Office Portal is installed and its web interface on ports 80/443 is network-accessible, the system is affected by this unauthenticated RCE vulnerability.
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 dataApply vendor-provided patches for Spectrum Power 4 and implement network segmentation to restrict web portal access to authorized personnel only, as this is a critical unauthenticated RCE in an industrial control system.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6579 — 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-2019-6579 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