yum does not properly handle bad metadata, which allows an attacker to cause a denial of service and possibly have other unspecified impact via a Trojan horse file in the metadata of a remote repository.
CVE-2013-1910
CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-05. NVD baseline CVSS 9.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.5%CVSS: 9.8Exploit: None knownExposed services: —
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
Internet exposure
The internet-exposure footprint is temporarily unavailable — the KEV-Exposure radar's record for this CVE could not be loaded just now. That is not a finding of zero exposed services; please retry shortly.
- CVSS v3
- 9.8
- EG Score
- 9.8CRITICALmedium confidence
- EG Risk
- 50EG Risk 50/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation3% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix. - EPSS PROB
- 2.5%
- EPSS %ILE
- 84th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 31, 2019
Last Modified
November 21, 2024
Advisory Details (1)
Auto-updated Sep 30, 2026No fix on record yet. Sources: redhat.
9.8
CRITICAL
2019-10-31 19:15:10.61+00
Affected: [{"url": "http://www.openwall.com/lists/oss-security/2013/03/29/4", "tags": ["Mailing List", "Third Party Advisory"], "source": "[email protected]"}, {"url": "http://www.securityfocus.com/bid/58533", "tags": ["Third Party Advisory", "VDB Entry"], "source": "[email protected]"}, {"url": "https://access.redhat.com/security/cve/cve-2013-1910", "tags": ["Third Party Advisory"], "source": "[email protected]"}, {"url": "https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-1910", "tags": ["Issue Tracking", "Third Party Advisory"], "source": "[email protected]"}, {"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/83348", "tags": ["Third Party Advisory", "VDB Entry"], "source": "[email protected]"}, {"url": "https://security-tracker.debian.org/tracker/CVE-2013-1910", "tags": ["Third Party Advisory"], "source": "[email protected]"}, {"url": "http://www.openwall.com/lists/oss-security/2013/03/29/4", "tags": ["Mailing List", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://www.securityfocus.com/bid/58533", "tags": ["Third Party Advisory", "VDB Entry"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/security/cve/cve-2013-1910", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-1910", "tags": ["Issue Tracking", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/83348", "tags": ["Third Party Advisory", "VDB Entry"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://security-tracker.debian.org/tracker/CVE-2013-1910", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}]
yum does not properly handle bad metadata, which allows an attacker to cause a denial of service and possibly have other unspecified impact via a Trojan horse file in the metadata of a remote repository.Vendor Advisories for CVE-2013-1910
Vendor advisories for this CVE are temporarily unavailable — the list could not be loaded just now. That is not a sign that none exist; please retry shortly.
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2013-1910?
CVE-2013-1910 is a critical vulnerability published on October 31, 2019. yum does not properly handle bad metadata, which allows an attacker to cause a denial of service and possibly have other unspecified impact via a Trojan horse file in the metadata of a remote repository.
When was CVE-2013-1910 disclosed?
CVE-2013-1910 was first published on October 31, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-1910 actively exploited?
CVE-2013-1910 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.5% probability of exploitation in the next 30 days (84th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2013-1910?
CVE-2013-1910 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2013-1910?
No fix for CVE-2013-1910 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2013-1910
Is Your Infrastructure Affected by CVE-2013-1910?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.