CVE-2020-11547
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 · uneditedPRTG Network Monitor before 20.1.57.1745 allows remote unauthenticated attackers to obtain information about probes running or the server itself (CPU usage, memory, Windows version, and internal statistics) via an HTTP request, as demonstrated by type=probes to login.htm or index.htm.
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 confidencePRTG Network Monitor before version 20.1.57.1745 contains an information disclosure vulnerability where unauthenticated remote attackers can obtain sensitive system information (CPU usage, memory usage, Windows version, and internal statistics) by sending HTTP requests with the parameter 'type=probes' to login.htm or index.htm.
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< 20.1.57.1745CVSS 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.
-
Confirm PRTG Network Monitor is installedCheck if the PRTG Network Monitor service is running on the system, or verify the PRTG web interface is accessible on the server (typically ports 80 or 443)Affected if PRTG Network Monitor is installed and running with its web interface accessible on the network
-
Identify the installed PRTG versionAccess the PRTG web interface and navigate to Setup > System Administration > System Status, or check the version information from the PRTG administrative interfaceAffected if The installed version is any version prior to 20.1.57.1745
-
Verify web interface accessibilityAttempt to access the PRTG login page (login.htm) from a non-authenticated browser request to confirm the web interface is reachableAffected if The web interface is accessible without authentication from the network where the check is performed
-
Test for vulnerable endpoint exposureSend an HTTP GET request to login.htm or index.htm with the query parameter 'type=probes' (e.g., http://[target]/login.htm?type=probes) without providing credentialsAffected if The server returns sensitive system information such as CPU usage, memory usage, Windows version, or internal statistics in the response
The environment is affected if PRTG Network Monitor version is below 20.1.57.1745 and the web interface is network-accessible without requiring 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 data20.1.57.1745
Upgrade PRTG Network Monitor to version 20.1.57.1745 or later. As an interim control, restrict network access to the PRTG web interface using firewall rules or network segmentation to prevent unauthorized access.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11547 — 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-11547 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