Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2019-13627 medium CVSS 6.3

Vulnerability in Ubuntu Linux (CVE-2019-13627)

Summary

Vulnerability in Ubuntu Linux (CVE-2019-13627). Confidential information can be exposed externally.

Original description

The description as published by the source.

It was discovered that there was a ECDSA timing attack in the libgcrypt20 cryptographic library. Version affected: 1.8.4-5, 1.7.6-2+deb9u3, and 1.6.3-2+deb8u4. Versions fixed: 1.8.5-2 and 1.6.3-2+deb8u7.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

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 CVE-2019-13627 has been found in Ubuntu Linux.
Confidential information can be exposed externally. CVSS score: 6.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Ubuntu Linux CVE-2019-13627" on the vendor's site.

CVE-2019-13627 (Ubuntu Linux) — CWE-203 / CVSS v3 6.3
Attack vector: local / unauthenticated
Affected: 1.8.4 - 5
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.

❓ What is the problem

A vulnerability (CWE-203) exists in Ubuntu Linux.

📍 Affected scope

Affected versions of Ubuntu Linux: 1.8.4 - 5.

🔥 Severity

Severity: Medium (CVSS 6.3/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory. (If a vulnerable version 1.8.4 - 5 is in production, plan an immediate maintenance window.)

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Ubuntu Linux を使っているサービスとバージョンを洗い出す。

  2. 2
    Match against affected range verify 
    Confirm if version satisfies `1.8.4 - 5`

    Step 1 で見つかったバージョンが影響範囲 1.8.4 - 5 に該当するか照合。本番で稼働中ならインシデント扱い。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details