Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2019-5482 critical CVSS 9.8

Vulnerability in CVE-2019-5482 (CVE-2019-5482)

Summary

vulnerability in CVE-2019-5482 (CVE-2019-5482). Risk of unauthorized operations or information disclosure. Exploitable via OACK.

Original description

The description as published by the source.

Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.

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 weakness called CVE-2019-5482 was discovered in Oracle Http Server.
Severity is Critical (CVSS 9.8/10). If exploited, attackers can fully take over the affected system.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "Oracle CVE-2019-5482".

CVE-2019-5482 (Oracle Http Server). Severity: Critical / CVSSv3 9.8. Category: CWE-122.
Response plan:

  1. Check the vendor advisory for affected versions and the patched release.
  2. If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
  3. If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
  4. Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
    PoCs and fix commits: see the 'References' section, MITRE, and NVD.
❓ What is the problem

A weakness (CVE-2019-5482) in Oracle Http Server. A serious software flaw has been identified.

📍 Affected scope

Target versions of Oracle Http Server (see vendor advisory). If running in production, identify exposure immediately.

🔥 Severity

Severity: Critical (CVSS 9.8/10). If exploited, attackers can fully take over the affected system.

🔧 How to fix

Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-122)

🛡️ Workaround

If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.

🔍 Detection

Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.

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.

    依存マニフェストで影響コンポーネントを特定する。

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

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

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