CVE-2018-25142
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 · uneditedNovaRad NovaPACS Diagnostics Viewer 8.5.19.75 contains an unauthenticated XML External Entity (XXE) injection vulnerability in XML preference import settings. Attackers can craft malicious XML files with DTD parameter entities to retrieve arbitrary system files through an out-of-band channel 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 · high confidenceNovaRad NovaPACS Diagnostics Viewer 8.5.19.75 has an unauthenticated XXE injection vulnerability in its XML preference import feature. Attackers can craft malicious XML files with DTD parameter entities to exfiltrate arbitrary system files via an out-of-band (OOB) channel. The critical severity (CVSS 9.8) stems from the lack of authentication required for exploitation combined with the ability to read sensitive system files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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 NovaPACS installation and versionLocate NovaPACS installation directory (commonly in C:\Program Files\NovaRad or C:\Novarad) and check the version information in the application's About or version file, or query the Windows registry under HKLM\SOFTWARE\Novarad\NovaPACS for the installed versionAffected if The installed version matches 8.5.19.75 or falls within an unpatched version range of NovaPACS Diagnostics Viewer
-
Verify XML preference import feature is enabledCheck if the application's XML preference import functionality is accessible through the web interface (typically /preferences/import or similar endpoint) or local client interfaceAffected if The XML preference import feature is present and accessible in the installed version
-
Confirm network accessibility of the XML import endpointIdentify the network ports used by NovaPACS (commonly web ports 80/443 or custom ports) and verify if the XML preference import endpoint is reachable from network locationsAffected if The XML preference import functionality is exposed over the network without authentication requirements
-
Inspect XML parser configurationExamine the application's configuration files (typically in config or settings directories) for XML parser settings, specifically looking for external entity processing or XXE-related configuration parametersAffected if The XML parser is configured to allow external entity processing or DTD parameter entities (XXE vulnerabilities exist when this is enabled)
A system is affected if it runs NovaPACS Diagnostics Viewer version 8.5.19.75 or an unpatched version with the XML preference import feature accessible and the XML parser configured to allow external entity processing.
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 dataDisable or restrict XML preference import functionality until a vendor patch is available, and configure the XML parser to disable external entity processing. Implement proper input validation and authentication for XML import features.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-25142 — 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-2018-25142 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