dbcve.org
Case SuiteApplication · Sauter Controls

CVE-2018-17912

HIGH · 7.5 CVSS v3.0 Published 2018-11-02
Fix available
A fix is available. Upgrade to after 3.10 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An XXE vulnerability exists in CASE Suite Versions 3.10 and prior when processing parameter entities, which may allow remote file disclosure.

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 confidence

CASE Suite versions 3.10 and prior contains an XXE vulnerability when processing XML parameter entities, allowing attackers to potentially read arbitrary files on the server by injecting malicious external entity references into XML input.

MitigationUpgrade CASE Suite beyond version 3.10, or if no patch is available, disable external entity processing in the XML parser and implement input validation for XML documents.

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
Case SuiteApplication
Affected:<= 3.10

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
None
Availability
None

CVSS:3.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed CASE Suite version
    Check the application version through the software itself (typically found in Help > About or the installer properties), or locate version information in installation directories and registry entries related to Sauter Controls CASE Suite.
    Affected if The installed version is 3.10 or lower.
  2. Identify XML processing functionality in use
    Locate any CASE Suite configurations, import settings, or modules that handle XML files. Review user-accessible XML import features or automated XML processing workflows within the application.
    Affected if XML import, parameter entity processing, or XML-based data exchange features are enabled or actively used.
  3. Inspect XML parser configuration
    Examine CASE Suite configuration files and XML parser settings for external entity processing configuration. Look for XML parser configuration files or settings that control entity resolution and external reference handling.
    Affected if The XML parser is configured to process external entities or parameter entities without restriction.

A user is affected if they are running CASE Suite version 3.10 or lower and have XML processing functionality enabled, as the vulnerable XML parser allows external entity injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 3.10
Interim mitigation

Upgrade CASE Suite beyond version 3.10, or if no patch is available, disable external entity processing in the XML parser and implement input validation for XML documents.

Fix this in Case Suite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-17912 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-17912 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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