Yum

Vendor:

First CVE: Jan 26, 2014 · Active for 12 years

2

Total CVEs

More Total CVEs than 49% of tracked products

1.0

Avg CVEs / Year

Bottom 1%

7.4

Avg CVSS

Higher Avg CVSS than 49% of tracked products

0.0%

KEV Rate

Bottom 1%

Trends Over Time

The number and severity of CVEs published that impact Yum over time

Volume of CVEsAvg CVSS Base Score

First CVE

Jan 26, 2014

12 years ago

Most Recent CVE

Oct 31, 2019

2,459 days ago

CVE Severity & Scoring

Yum2 CVEs

50%

All CVEs352,427 CVEs

45%

40%

11%

MediumCritical

Attack Vector

Local0 (0.0%)

Network1 (50.0%)

Unknown1 (50.0%)

Physical0 (0.0%)

Adjacent Network0 (0.0%)

Attack Complexity

Low1 (50.0%)

High0 (0.0%)

Unknown1 (50.0%)

User Interaction

None1 (50.0%)

Unknown1 (50.0%)

Required0 (0.0%)

Privileges Required

Low0 (0.0%)

High0 (0.0%)

None1 (50.0%)

Unknown1 (50.0%)

Top CVEs

Signals from CVEs in this product scope (2 CVEs).

2 CVEs · Highest risk first

CVE	Published	CVSS	Risk	KEV	Exploit
CVE-2013-1910CRITICAL 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	Oct 31, 2019	9.8	25	NO	NO
CVE-2014-0022MEDIUM The installUpdates function in yum-cron/yum-cron.py in yum 3.4.3 and earlier does not properly check the return value of the sigCheckPkg function, which allows remote attackers to	Jan 26, 2014	5.0	18	NO	NO

View all 2 CVEs →

Exploit Exposure

Signals from CVEs in this product scope (2 CVEs).

CISA KEV

0 CVEs

0.0% of CVEs· Bottom 1%

Metasploit

0 CVEs

0.0% of CVEs· Bottom 1%

Nuclei

0 CVEs

0.0% of CVEs· Bottom 1%

ExploitDB

0 CVEs

0.0% of CVEs· Bottom 1%

Social Chatter

Signals from CVEs in this product scope (2 CVEs).

Media Mentions

Signals from CVEs in this product scope (2 CVEs).

Top CNAs Publishing CVEs For Yum

Top CWEs

Versions

Version	CVE Count	Avg CVSS	Avg EPSS
3.4.3	1	9.8	2.5%
3.4.2	1	5.0	2.4%
3.4.1	1	5.0	2.4%
3.4.0	1	5.0	2.4%