CVE-2020-10605
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 · uneditedGrundfos CIM 500 before v06.16.00 responds to unauthenticated requests for password storage files.
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 confidenceThe Grundfos CIM 500 (a pump controller communication interface module) before version v06.16.00 responds to unauthenticated HTTP requests seeking password storage files. An attacker without credentials can retrieve these files, potentially exposing stored authentication credentials for the device or connected systems.
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< 06.16.00CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Grundfos CIM 500 devices on your networkScan your network for devices with Grundfos CIM 500 indicators, or review asset inventory to locate these modules. Check for devices responding on HTTP ports (typically 80/443) with Grundfos-specific web interfaces or SNMP community strings containing 'grundfos'.Affected if A Grundfos CIM 500 device exists in your environment and is network-accessible.
-
Check the firmware versionAccess the device web interface (HTTP/HTTPS) and navigate to the firmware or system information page, or use SNMP to query the device firmware version OID if available. Compare the displayed version against 06.16.00.Affected if The installed firmware version is lower than 06.16.00.
-
Verify HTTP service accessibilityAttempt to reach the device HTTP interface from an untrusted network segment or perform a port scan targeting port 80/443 on the device IP address.Affected if The HTTP service is exposed and reachable from a network segment where untrusted users could send requests.
-
Test for unauthenticated password file accessUsing a web browser or curl command, send an unauthenticated HTTP GET request to common password file paths such as /passwords, /config/passwords, /etc/passwd, or paths ending in .pwd, .dat, or .xml that may contain stored credentials. If the device returns HTTP 200 with file content, the vulnerability is present.Affected if The device returns password storage files without requiring authentication.
You are affected if a Grundfos CIM 500 device with firmware below v06.16.00 is accessible over HTTP and returns password storage files without authentication.
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 data06.16.00
Update Grundfos CIM 500 to firmware version v06.16.00 or later. If immediate patching is not feasible, implement network segmentation to restrict access to the device to only trusted hosts and monitor for unauthorized access attempts.
- Consultation4.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10605 — 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-10605 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