Vulnerability in libcrypto++
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as DEBIAN-CVE-2019-14318 has been found in libcrypto++.
Confidential information can be exposed externally.
What to do: upgrade libcrypto++ to 5.6.4-9 or later.
If unsure, ask your IT team or search "libcrypto++ DEBIAN-CVE-2019-14318" on the vendor's site.
DEBIAN-CVE-2019-14318 (libcrypto++)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.6.4-9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in libcrypto++.
Check the vendor advisory for the affected versions of libcrypto++.
Severity: ?. Confidential information can be exposed externally.
Update to 5.6.4-9.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'libcrypto++' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'libcrypto++' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
libcrypto++を grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade libcrypto++ to 5.6.4-9ステージング環境で 5.6.4-9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Debian:12 | libcrypto++ |
< 5.6.4-9 |
5.6.4-9 |
| Debian:13 | libcrypto++ |
< 5.6.4-9 |
5.6.4-9 |
| Debian:14 | libcrypto++ |
< 5.6.4-9 |
5.6.4-9 |
Original description The description as published by the source.
Crypto++ 8.3.0 and earlier contains a timing side channel in ECDSA signature generation. This allows a local or remote attacker, able to measure the duration of hundreds to thousands of signing operations, to compute the private key used. The issue occurs because scalar multiplication in ecp.cpp (prime field curves, small leakage) and algebra.cpp (binary field curves, large leakage) is not constant time and leaks the bit length of the scalar among other information.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory security-tracker.debian.org