# CVE-2014-8587: Security feature bypass in n/a

> Remote attackers can spoof Digital Signature Algorithm signatures in SAP cryptographic libraries, bypassing security controls.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Nov 2014
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qvm2-xc63-59fm

## What is CVE-2014-8587?

CVE-2014-8587 is a high-severity vulnerability in Sap Netweaver, published on 4 Nov 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SAPCRYPTOLIB 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.

Weakness: CWE-310

## Which versions are affected by CVE-2014-8587?

It affects 5 products.


Products: Sap Commoncryptolib, Sap Hana, Sap Netweaver, Sap Sapcryptolib, Sap Sapseculib.

## How do I fix CVE-2014-8587?

No fix has been published for CVE-2014-8587 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-8587 being exploited?

There is no known exploitation of CVE-2014-8587 in the wild and no public exploit code.

## Other vulnerabilities in Sap Netweaver

- [CVE-2023-40309](https://insights.sbomify.com/CVE-2023-40309/): Missing Authorization check in SAP CommonCryptoLib (critical 9.8)
- [CVE-2023-40308](https://insights.sbomify.com/CVE-2023-40308/): Memory Corruption vulnerability in SAP CommonCryptoLib (high 7.5)
- [CVE-2021-38177](https://insights.sbomify.com/CVE-2021-38177/): Null dereference in SAP CommonCryptoLib (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-8587 and fix it if it is affected.

What it is: CVE-2014-8587 is a high-severity vulnerability in Sap Netweaver, published on 4 Nov 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-8587 in the wild and no public exploit code.

Affected product: Sap Netweaver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-8587/ (Markdown: https://insights.sbomify.com/CVE-2014-8587/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-8587
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-8587
- OSV: https://osv.dev/vulnerability/CVE-2014-8587

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-8587/
Summaries are generated and may contain mistakes; the official description above is the record.