CVE-2023-32782
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 command injection was identified in PRTG 23.2.84.1566 and earlier versions in the Dicom C-ECHO sensor where an authenticated user with write permissions could abuse the debug option to write new files that could potentially get executed by the EXE/Script sensor. The severity of this vulnerability is high and received a score of 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 confidenceA command injection vulnerability in PRTG Network Monitor's Dicom C-ECHO sensor (versions 23.2.84.1566 and earlier) allows authenticated users with write permissions to abuse the debug option to write arbitrary files to disk, which can subsequently be executed by the EXE/Script sensor, leading to remote code execution.
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< 23.3.86.1520CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 PRTG Network Monitor versionAccess the PRTG web interface and navigate to Setup > System Administration > System Status, or check the about page. Alternatively, look for the version information in the PRTG installation directory or registry.Affected if The installed version is earlier than 23.3.86.1520 (or 23.2.84.1566 and earlier)
-
Locate Dicom C-ECHO sensor configurationsIn the PRTG web interface, navigate to the device tree and search for sensors of type Dicom C-ECHO, or check the sensor list under each device for Dicom-related sensors.Affected if One or more Dicom C-ECHO sensors are actively configured or added to devices in the monitoring environment
-
Inspect Dicom C-ECHO sensor debug settingsOpen each Dicom C-ECHO sensor settings page and examine the Debug Options section. Look for settings related to debug mode, file writing, or custom parameters that allow file manipulation.Affected if Debug options are enabled or configurable, particularly options that allow writing files to disk
-
Verify user permissions on Dicom sensorsIn PRTG, go to Setup > Account Settings > User Accounts and Groups, or check the sensor's access rights. Review which users or groups have write permissions to the Dicom C-ECHO sensors.Affected if Authenticated users with write permissions exist, especially non-administrator accounts
-
Check EXE/Script sensor configurationReview EXE/Script sensor settings to confirm they can execute files written by other sensors. Check the security context and execution permissions for these sensors.Affected if EXE/Script sensors are configured to run scripts or executables, and the execution path overlaps with locations the Dicom sensor can write to
The environment is affected if PRTG version is earlier than 23.3.86.1520 AND a Dicom C-ECHO sensor with debug options is configured, allowing authenticated users to write executable files that the EXE/Script sensor can run.
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.
dbcve · scoped23.3.86.1520
Restrict or revoke write permissions for the Dicom C-ECHO sensor, disable debug options if not required, and ensure the EXE/Script sensor runs with least-privilege principles; upgrade to a patched version once available.
PRTG Network Monitor version 23.3.86.1520 or later
- 1. Backup the current PRTG Network Monitor configuration using the built-in backup feature or by copying the configuration database files.
- 2. Download PRTG Network Monitor version 23.3.86.1520 or later from the official Paessler download page at www.paessler.com.
- 3. Run the installer on the PRTG server and follow the upgrade wizard prompts.
- 4. After installation completes, verify the new version by checking Help > About PRTG Network Monitor.
- 5. Log in as an administrator and navigate to the Dicom C-ECHO sensor settings to confirm the debug option has been properly remediated.
- 6. Test that the Dicom C-ECHO sensor functions correctly and that the EXE/Script sensor cannot execute arbitrarily written files.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32782 — 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-2023-32782 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