CVE-2018-19005
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 · uneditedCscape, Version 9.80.75.3 SP3 and prior. An improper input validation vulnerability has been identified that may be exploited by processing specially crafted POC files lacking user input validation. This may allow an attacker to read confidential information and remotely execute arbitrary code.
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 confidenceCscape versions 9.80.75.3 SP3 and prior contain an improper input validation vulnerability in POC file processing. When the software parses specially crafted POC files without validating user input, it allows attackers to read confidential information and achieve 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< 9.80.75.3= 9.80.75.3CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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.
-
Locate Cscape installationCheck standard installation paths such as C:\Program Files\Hornerautomation\Cscape or C:\Program Files (x86)\Hornerautomation\Cscape, or search for cscape.exe using file explorer or PowerShell command: Get-ChildItem -Path 'C:\' -Filter 'cscape.exe' -Recurse -ErrorAction SilentlyContinueAffected if Cscape software is found on the system
-
Identify installed Cscape versionRight-click on cscape.exe, select Properties, then go to the Details tab to view the File Version. Alternatively, right-click the Cscape shortcut in the Start Menu and check the target path for version information, or open Cscape and navigate to Help > AboutAffected if The version number is 9.80.75.3 or lower (including any SP3 variant of 9.80.75.3)
-
Check for POC file associationSearch for .poc files on the system using PowerShell: Get-ChildItem -Path 'C:\Users' -Filter '*.poc' -Recurse -ErrorAction SilentlyContinue. Also check file type associations in Windows Registry under HKCR\.pocAffected if POC files exist on the system or .poc file extension is registered as associated with Cscape
-
Verify POC file parsing capabilityLaunch Cscape and attempt to open a POC file via File > Open, or check if POC appears in the file open dialog filter. Review Cscape documentation or help menu for POC functionalityAffected if POC file parsing feature is present and functional in the installed Cscape version
You are affected if Cscape is installed with a version of 9.80.75.3 or any version lower than 9.80.75.3, and the POC file parsing feature is available on your system.
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 data9.80.75.3
Restrict opening untrusted POC files and apply any vendor-supplied patches when available. Until a patch is released, implement additional input validation on file parsing routines or isolate affected systems network-wise.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19005 — 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-19005 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