CVE-2020-15790
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 (All versions < V4.70 SP8). If configured in an insecure manner, the web server might be susceptible to a directory listing attack.
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 confidenceA directory listing vulnerability exists in Spectrum Power 4 (all versions < V4.70 SP8). When the web server is configured in an insecure manner, it may allow attackers to enumerate files and directories by obtaining directory listings, potentially exposing sensitive system files or configuration data.
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< 4.70= 4.70CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Spectrum Power 4 versionLocate the installed Spectrum Power 4 version through the product's about dialog, installation directory, or system information panel. Common paths include the program files directory or configuration files named version.info or similar.Affected if The installed version is lower than 4.70 SP8, or exactly 4.70 (without SP8).
-
Locate web server configuration fileFind the web server configuration file (typically httpd.conf, .htaccess, or the Spectrum Power web configuration) used by the Spectrum Power 4 installation. Check the conf or config subdirectories within the Spectrum Power installation path.Affected if The web server configuration file exists and contains directory directive settings.
-
Verify directory listing configurationOpen the web server configuration file and search for 'Options' directives or directory blocks. Check whether the 'Indexes' option is present within these directives.Affected if The configuration contains 'Indexes' in an Options directive for a directory accessible via the web server, indicating directory listing is enabled.
-
Test directory listing accessibilityUsing a web browser or curl command, attempt to access a directory path under the Spectrum Power web root (for example, http://[hostname]/[spectrum-web-path]/) without specifying a file name.Affected if The web server returns a directory listing showing file names rather than a 403 Forbidden or 404 Not Found error, confirming the vulnerability is exploitable.
A user is affected if their Spectrum Power 4 version is below V4.70 SP8 AND the web server has directory listing enabled (Indexes option present), allowing unauthenticated enumeration of files and directories.
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 data4.70
Upgrade to Spectrum Power 4 V4.70 SP8 or later. Additionally, ensure the web server configuration disables directory listing (e.g., remove Indexes option from directory directives).
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15790 — 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-2020-15790 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