CVE-2014-8587
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 · uneditedSAPCRYPTOLIB before 5.555.38, SAPSECULIB, and CommonCryptoLib before 8.4.30, as used in SAP NetWeaver AS for ABAP and SAP HANA, allows remote attackers to spoof Digital Signature Algorithm (DSA) signatures via unspecified vectors.
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 confidenceThe vulnerability exists in SAP's cryptographic libraries (SAPCRYPTOLIB, SAPSECULIB, and CommonCryptoLib) used for digital signature operations. An attacker can spoof DSA signatures, potentially allowing impersonation of legitimate users or signing of malicious content as a trusted entity.
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<= 8.4.29<= 5.555.37all versionsall versionsall versionsCVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 the SAP cryptographic library in useExamine the SAP system for presence of CommonCryptoLib (libsapcrypto.so, sapcrypto.dll), SAPCRYPTOLIB (sapcryptolib.dll), or SAPSECULIB (sapseculib.dll) files in the system directoriesAffected if Any of these libraries are present on the system
-
Determine CommonCryptoLib versionCheck the version of libsapcrypto.so or sapcrypto.dll - typically found in the SAP installation directory under /usr/sap or the Windows SAP directory. Use file properties or strings command to extract version infoAffected if Version is 8.4.29 or lower
-
Determine SAPCRYPTOLIB versionCheck the version of sapcryptolib.dll or the associated library files. Query via SAP kernel version utilities or examine file propertiesAffected if Version is 5.555.37 or lower
-
Confirm SAPSECULIB usageVerify if the system utilizes SAPSECULIB for cryptographic operations by examining SAP configuration files or transaction code SSF (Security Functions)Affected if SAPSECULIB is configured for signature operations - all versions affected
-
Check if DSA signature operations are activeReview SAP profile parameters (ssf/ssf_api, ssf/name), transaction code SF01 for signature creation, or examine application logs for DSA-based signature verification activityAffected if DSA algorithm is being used for digital signatures in the SAP environment
-
Identify SAP Hana or Netweaver deploymentVerify the SAP system type via transaction SM51 (Netweaver) or check Hana database version via HDB version or SAP HANA StudioAffected if System runs SAP Hana or Netweaver with the vulnerable cryptographic libraries present
The environment is affected if any SAP cryptographic library (CommonCryptoLib <= 8.4.29, SAPCRYPTOLIB <= 5.555.37, or SAPSECULIB of any version) is present and DSA-based digital signature operations are being performed on SAP Hana or Netweaver systems.
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 dataUpdate SAPCRYPTOLIB to version 5.555.38 or later, and CommonCryptoLib to version 8.4.30 or later. Apply via SAP notes and perform signature verification testing after patching.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.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 $11,008.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8587 — 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-2014-8587 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