CVE-2018-2487
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 · uneditedSAP Disclosure Management 10.x allows an attacker to exploit through a specially crafted zip file provided by users: When extracted in specific use cases, files within this zip file can land in different locations than the originally intended extraction point.
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 confidenceSAP Disclosure Management 10.x contains a path traversal vulnerability during zip file extraction (zip slip). Specially crafted zip files containing entries with '../' sequences in their file paths allow attackers to write files outside the intended extraction directory, potentially overwriting system files or exposing sensitive data.
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= 10.1CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/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 installed SAP Disclosure Management versionCheck the installed version of SAP Disclosure Management in the system (typically via SAP LM or installed programs list). On Windows, check Add/Remove Programs or the installation directory for version information.Affected if The installed version is exactly 10.1 (version 10.1) - other versions may have different vulnerability status.
-
Determine if zip extraction feature is usedReview application logs, user activity records, or configuration settings to see if the zip file extraction feature of SAP Disclosure Management has been used.Affected if The zip extraction feature has been used to extract untrusted zip files - this is required for exploitation.
-
Inspect extraction output directoriesExamine the directories where zip files are typically extracted by the application. Look for any files that appear outside the intended extraction folder or that were created at unexpected paths.Affected if Files exist outside the intended extraction directory, or files with paths containing '../' patterns are present in the extraction output.
-
Check for unauthorized system file modificationsReview critical system files or configuration files that could be targeted by path traversal. Compare current file hashes or timestamps against known good baselines.Affected if System files or configuration files outside the extraction directory have been modified, especially around the time of zip extraction activities.
You are affected if SAP Disclosure Management version 10.1 is installed AND the zip extraction feature has been used with untrusted zip files, resulting in files written outside the intended directory.
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 dataImplement strict validation of zip entry paths before extraction, ensuring all extracted paths resolve within the intended directory. Sanitize or reject any entries containing '..' sequences or absolute paths. Apply available vendor patches.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-2487 — 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-2487 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