CVE-2018-0659
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 · uneditedDirectory traversal vulnerability in ver.2.8.4.0 and earlier and ver.3.3.0.0 and earlier allows an attacker to create or overwrite existing files via specially crafted ATC file.
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 directory traversal vulnerability in the ATC file parser allows attackers to use path traversal sequences (like '../') in specially crafted ATC files to create or overwrite arbitrary files on the system outside the intended directory.
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<= 2.8.4.0>= 3.0.0.0, <= 3.3.0.0CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/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.
-
Locate Hibara Attachecase installationCheck for the presence of Hibara Attachecase software on the system by searching for the application in the installed programs list or common installation directories such as C:\Program Files\ or C:\Program Files (x86)\.Affected if Hibara Attachecase is installed on the system
-
Determine installed version numberOpen the Windows Control Panel, navigate to Programs and Features, find Hibara Attachecase in the list, and note the version number displayed in the Version column. Alternatively, right-click the executable file and select Properties to view the version information on the Details tab.Affected if The version cannot be determined or the software is installed without a clear version identifier
-
Compare version against affected rangesCompare your installed version to the affected ranges: version 2.8.4.0 or lower, OR any version from 3.0.0.0 through 3.3.0.0. Any version 2.8.5.0 through 2.9.x.x or 3.3.1.0 and above is NOT affected.Affected if The installed version falls within <= 2.8.4.0 OR the range >= 3.0.0.0 AND <= 3.3.0.0
-
Verify ATC file parsing capabilityConfirm that the Attachecase application includes functionality to parse or open ATC files, as this vulnerability specifically affects the ATC file parser component.Affected if The application has ATC file parsing capabilities and the version is within the affected ranges
The user is affected if Hibara Attachecase is installed with a version number that is either 2.8.4.0 or lower, or falls between 3.0.0.0 and 3.3.0.0 inclusive, and the application is used to open ATC files.
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 dataUsers should avoid opening untrusted ATC files from unknown sources; implement proper path canonicalization and validation to ensure file paths stay within intended directories.
- 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-0659 — 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-0659 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